[fpc-devel] One fpc.cfg per fpc version

[Tomas Hajny]

On Mon, February 17, 2014 15:15, Mattias Gaertner wrote:
> On Mon, 17 Feb 2014 14:14:03 +0100
> "Tomas Hajny" <XHajT03 at hajny.biz> wrote:
 .
 .
>> Still, my open question is: what are the drivers for needing to support
>> (=
>> having to maintain) different fpc.cfg files for different FPC versions?
>> Moreover - if people use different approaches and want to have different
>> versions and different locations (differing per distribution, user
>> preferences, etc.), can't you simply let them to choose their preferred
>> approach in Lazarus explicitly (either using single fpc.cfg for
>> everything, or having version specific files configured explicitly by
>> the
>> user when setting path to his FPC installations)?
>
> Well, I thought too that those two approaches are enough.
> But people use -FD, -Xp, -V, @, PATH, PP, PPC_CONFIG_PATH,
> PPC_EXEC_PATH, symlinks, scripts, etc. I wonder if Lazarus should
> provide GUI elements for them.

I'm not sure whether all these approaches used from the command line need
to be catered for by Lazarus. Some of them (e.g. script and symlink
solutions for selecting a particular version) are in fact directly
replaced by Lazarus _when_using_Lazarus_ (users may obviously continue
using them from the command line to address their specific needs there).
People creating such solutions for themselves should probably understand
well that the behaviour with Lazarus may be different and do not expect
Lazarus to reverse engineer their scripts. ;-) BTW, the same is true for
the text mode IDE and the command line compiler.

Tomas