On 13/08/2012 10:22, Ludo Brands wrote:
IMHO this lazset is the IDE itself. If the installer creates 2
startupmenu entries: one normal, and one with forced setup
Having "lazset"=IDE is indeed the easiest to maintain. But to accomodate 3rd
party setup programs like fpcup, codetyphon(?), it would be nice if the IDE
could be told what the setup params are instead of doing a forced setup.
Compiler, fpc sources, debugger and perhaps language are known by these
installers. Having something like a lazarus --setup="gdb=path-to-gdb
language=the-language fpc=path-to-compiler ..." which sets the corresponding
values in the lazarus configuration (eventually specified with --pcp) and
doesn't launch the ide (returns immediately) would be a good compromise.
The need to specify such params should only apply to the 1st start of an
installation (or a new primary-conf....)
Once a config exists, the values are (IIRC) taken from there, and
updates (eg reset language) are to be made by the user.
There is no need to specify first time setup on the command line. That
is what the environmentopts.xml in the exe directory (secondary conf) is
for.
If the IDE does not find a config, it looks for this.
So custom installers can provide there own settings there. (by means of
editing the XML file, or replacing it (might loose new settings added to it)
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
