[Lazarus] Run parameters

Kostas Michalopoulos badsectoracula at gmail.com
Sat Feb 11 14:25:55 CET 2017

I think having a list for run modes (i assume you mean the settings you
specify in the Run -> Run Parameters dialog box) that you can select from a
popup menu near the "play" button and have different run modes apply, like
you can select the build mode from the "gear" button, is a good idea. Being
able to switch configuration files and working directories from inside
Lazarus for some of the tools i work with would be very nice.

The only thing i disagree with is to have them per build mode since chances
are you'd need them with different build modes (e.g. debug, release,
profile, etc would have the same run modes) and even if you could copy
them, it would still be an annoyance to make sure all are available.

Instead i'd say to have a table with a column per build mode and a row per
run mode, have checkboxes for those that will apply and those checkboxes
would be enabled by default.

Alternatively just use a global list that is the same across all build
modes, but then you may have run modes that do not apply in all build modes
and have them take up space (e.g. if one of your run modes causes a program
to load a 32bit DLL and you are in a build mode that explicitly targets a
64bit OS this run mode wouldn't apply - of course one case wouldn't matter
much, but the next thing i imagine after such a feature is available is
being able to generate run modes automatically though a script :-P).


On Sat, Feb 11, 2017 at 1:15 PM, Michael Van Canneyt via Lazarus <
lazarus at lists.lazarus-ide.org> wrote:

> On Sat, 11 Feb 2017, Mattias Gaertner via Lazarus wrote:
> On Sat, 11 Feb 2017 11:22:23 +0100 (CET)
>> Michael Van Canneyt via Lazarus <lazarus at lists.lazarus-ide.org> wrote:
>> Hello,
>>> Currently, the options specified in 'Run - Parameters' are stored in the
>>> project.lpi file.
>>> I have always found this a strange choice.
>>> What is the rationale for this decision ?
>> Some projects need the same run parameters on all machines.
>> For example instantfpc projects can't run with the default run
>> params.
> From my personal experience, I really think this is a minority...
> For example, testsuites. I keep setting the --suite=TestA.MethodXYZ. My
> collegue sets it to --suite=TestB.MethodC. It gives me conflicts every time
> I update from SVN.
> And in this case you almost never use the same command-line twice.
> Logically, I would I think these parameters belong in the .lps file ?
>> I agree, there should be an option. Or even better would be a list
>> of run modes.
> Don't get overenthousiastic. Keep it simple :)
> The trouble with a list is that you must maintain it, just as the build
> modes. I don't want that.
> So if you do decide to introduce it, please keep it optional, as the build
> modes.
> Not to say there is already a list, namely the history mechanism.
>> Some developers using build modes suggested to have different run
>> parameters per build mode. So it would be nice if the list and build
>> modes can be connected. For example when switching the build mode, the
>> IDE automatically switches the run mode too.
> Well.  If you can give a global option
> Save "run parameter" settings in
> [*] .lpi file
> [ ] .lps file [ ] run modes
> [ ] build mode
> I will be satisfied. You could use the ones in .lpi as a fallback, in case
> they are not set in
> the .lps
> Michael.
> --
> _______________________________________________
> Lazarus mailing list
> Lazarus at lists.lazarus-ide.org
> http://lists.lazarus-ide.org/listinfo/lazarus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20170211/3dc7bff6/attachment-0003.html>

More information about the Lazarus mailing list