[Lazarus] Using different FPC versions

[Michael Van Canneyt]

On Mon, 10 Feb 2014, Mattias Gaertner wrote:

> On Mon, 10 Feb 2014 10:33:20 +0100 (CET)
> Michael Van Canneyt <michael at freepascal.org> wrote:
>
>> [...]
>> However, this can be avoided to a large extent by simply also adding the compiler version to the unit output path:
>> $(fpcversion)/$(cpu)-$(os)/$(widgetset)
>> or
>> $(cpu)-$(os)/$(widgetset)/$(fpcversion)
>> or even
>> $(fpcversion)-$(cpu)-$(os)/$(widgetset)
>
> The Lazarus macro for the FPC version (e.g. 2.6.2) is $FPCVer. Macro
> names are case insensitive. I know, you know that. :)

No, actually I don't. Which is why I wrote that the names may be fictitious :)

I never (actively) use IDE macros. Probably they get used in the background.

>> I could probably set this path manually in every package on my system.
>> Cumbersome, and would probably conflict with svn updates.
>>
>> Is there any plan to add such a feature by default, or have I missed something, and there is actually
>> an easier way than 2 separate installations to achieve the same effect, i.e. use 2 compiler versions
>> without requiring a restart and a complete recompile ?
>
> The "Additions and Overrides" of Lazarus 1.1+ can do that.
> I added it as an example:
> http://wiki.lazarus.freepascal.org/IDE_Window:_Compiler_Options#Change_the_output_directory_of_project_and_all_packages

Ah, in this completely un-understandable dialog. I am avoiding it like the plague :(

A GUI is meant to make things simpler, not complicate them, this dialog is IMHO a 
prime example of a violation of that principle. (somewhat like the MS Access visual query builder)

Since the presence of different compiler versions is a given for the lazarus ecosystem,
you might consider changing the defaults to what you propose in the example.

Thanks for the answer, and taking the trouble to provide an example :)

Michael.