Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2012-04

lazbuild --build-ide= --addpackage bla.lpk?

7 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Reinier Olislagers

Hi list,

At the moment, the fpcup tool can compile packages using lazbuild. It would be very nice if the compiled package could be added to the list of packages to be installed on IDE recompile.

Perhaps this functionality could better be placed in lazbuild so others using e.g. batch files can use it as well, making possible something like lazbuild --build-ide= --addpackage <somepackage.lpk> or perhaps only
lazbuild --addpackage <somepackage.lpk>
(with or without --primary-config-path)
to compile the package and add it to the package list.

Would this be a good idea to implement?

Regards,
Reinier

Reply by email

Mark Morgan Lloyd
to Reinier Olislagers
Reinier Olislagers wrote 15 lines
Hi list, At the moment, the fpcup tool can compile packages using lazbuild. It would be very nice if the compiled package could be added to the list of packages to be installed on IDE recompile. Perhaps this functionality could better be placed in lazbuild so others using e.g. batch files can use it as well, making possible something like lazbuild --build-ide= --addpackage <somepackage.lpk> or perhaps only lazbuild --addpackage <somepackage.lpk> (with or without --primary-config-path) to compile the package and add it to the package list. Would this be a good idea to implement?

I think so. I've previously hacked lazsvn into the sources so that a make bigide included it, but what I did wasn't pleasant and broke as soon as the package didn't track changes to trunk.

Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues]

Reply by email

Mattias Gaertner
to Reinier Olislagers: At the moment, the fpcup tool can compile packages using lazbuild. It would be very nice…

Reinier Olislagers hat am 23. April 2012 um 11:45 geschrieben:

Show quoted text 13 lines
Hi list, At the moment, the fpcup tool can compile packages using lazbuild. It would be very nice if the compiled package could be added to the list of packages to be installed on IDE recompile. Perhaps this functionality could better be placed in lazbuild so others using e.g. batch files can use it as well, making possible something like lazbuild --build-ide= --addpackage <somepackage.lpk> or perhaps only lazbuild --addpackage <somepackage.lpk> (with or without --primary-config-path) to compile the package and add it to the package list.

1. the syntax for long options is
--paramname=<value>

2. addpackage makes sense for projects too, so lazbuild without --build-ide is ambiguous.

3. Both should be possible:
--addpackage=<pkgname>
and
--addpackage=<path/pkgname.lpk>

Would this be a good idea to implement?

yes

Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120423/f57b05cb/attachment.html>

Reply by email

Reinier Olislagers
to Mattias Gaertner
Mattias Gaertner wrote 9 lines
Reinier Olislagers hat am 23. April 2012 um 11:45 geschrieben: > Perhaps this functionality could better be placed in lazbuild so others > using e.g. batch files can use it as well, making possible something like > lazbuild --build-ide= --addpackage <somepackage.lpk> > or perhaps only > lazbuild --addpackage <somepackage.lpk> > (with or without --primary-config-path) > to compile the package and add it to the package list.

Thanks Mattias,

Hope I'm not displaying too much ignorance here, but here goes:

1. the syntax for long options is --paramname=<value>

Got it.

2. addpackage makes sense for projects too, so lazbuild without --build-ide is ambiguous.

Do you mean adding a package based on the project you're compiling with lazbuild?

3. Both should be possible: --addpackage=<pkgname>

... so this would just add an already compiled package to the list of packages to be installed, right?

and --addpackage=<path/pkgname.lpk>

... which would compile the package, then add it to the list, yes?

Thanks,
Reinier

Reply by email

Mattias Gaertner
to Reinier Olislagers

Reinier Olislagers hat am 23. April 2012 um 13:19 geschrieben:

Show quoted text 24 lines
On 23-4-2012 12:49, Mattias Gaertner wrote: > Reinier Olislagers hat am 23. April 2012 > um 11:45 geschrieben: >> Perhaps this functionality could better be placed in lazbuild so others >> using e.g. batch files can use it as well, making possible something like >> lazbuild --build-ide= --addpackage <somepackage.lpk> >> or perhaps only >> lazbuild --addpackage <somepackage.lpk> >> (with or without --primary-config-path) >> to compile the package and add it to the package list. Thanks Mattias, Hope I'm not displaying too much ignorance here, but here goes: > 1. the syntax for long options is > > --paramname=<value> Got it. > 2. addpackage makes sense for projects too, so lazbuild without > --build-ide is ambiguous. Do you mean adding a package based on the project you're compiling with lazbuild?

Yes. You don't need to implement this now. Just keep this in mind that it might eventually be added.

Show quoted text 6 lines
> 3. Both should be possible: > > --addpackage=<pkgname> ... so this would just add an already compiled package to the list of packages to be installed, right?

No. If the package was not compiled lazbuild compiles it. A package name is enough. The lpi only contains names too.

Show quoted text 5 lines
> > and > > --addpackage=<path/pkgname.lpk> ... which would compile the package, then add it to the list, yes?

No. lazbuild compiles packages as needed. Unless you add the -B and -r option.

Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120423/c8adf84b/attachment-0001.html>

Reply by email

Reinier Olislagers
to Mattias Gaertner
Mattias Gaertner wrote 34 lines
Reinier Olislagers hat am 23. April 2012 um 13:19 geschrieben: > Thanks Mattias, > > Hope I'm not displaying too much ignorance here, but here goes: > > > 1. the syntax for long options is > > > > --paramname=<value> > Got it. > > > 2. addpackage makes sense for projects too, so lazbuild without > > --build-ide is ambiguous. > Do you mean adding a package based on the project you're compiling with > lazbuild? Yes. You don't need to implement this now. Just keep this in mind that it might eventually be added. > > 3. Both should be possible: > > > > --addpackage=<pkgname> > ... so this would just add an already compiled package to the list of > packages to be installed, right? No. If the package was not compiled lazbuild compiles it. A package name is enough. The lpi only contains names too. > > > > --addpackage=<path/pkgname.lpk> > ... which would compile the package, then add it to the list, yes? No. lazbuild compiles packages as needed. Unless you add the -B and -r option.

Thanks Mattias,
All clear now.

Regards,
Reinier

Reply by email

Reinier Olislagers
to Mattias Gaertner: Reinier Olislagers hat am 23. April 2012 um 13:19 geschrieben: Yes. You don't need to…
Mattias Gaertner wrote 52 lines
Reinier Olislagers hat am 23. April 2012 um 13:19 geschrieben: > On 23-4-2012 12:49, Mattias Gaertner wrote: > > Reinier Olislagers hat am 23. April 2012 > > um 11:45 geschrieben: > >> Perhaps this functionality could better be placed in lazbuild so others > >> using e.g. batch files can use it as well, making possible something like > >> lazbuild --build-ide= --addpackage <somepackage.lpk> > >> or perhaps only > >> lazbuild --addpackage <somepackage.lpk> > >> (with or without --primary-config-path) > >> to compile the package and add it to the package list. > > Thanks Mattias, > > Hope I'm not displaying too much ignorance here, but here goes: > > > 1. the syntax for long options is > > > > --paramname=<value> > Got it. > > > 2. addpackage makes sense for projects too, so lazbuild without > > --build-ide is ambiguous. > Do you mean adding a package based on the project you're compiling with > lazbuild? Yes. You don't need to implement this now. Just keep this in mind that it might eventually be added. > > > 3. Both should be possible: > > > > --addpackage=<pkgname> > ... so this would just add an already compiled package to the list of > packages to be installed, right? No. If the package was not compiled lazbuild compiles it. A package name is enough. The lpi only contains names too.

Patch in mantis 22128

When developing this, it seemed more natural to use the existing mechanism of specifying filenames (for projects/packages) to also allow package names, so the patch also extends support for compiling package by name (i.e. lazbuild rx instead of lazbuild
c:\development\somewhere\rx.lpk). Hope this can find favour ;)

Thanks,
Reinier

Reply by email