[fpc-devel] fpcmkcfg invocation for two versions (linux)

[Mark Morgan Lloyd]

Marco van de Voort wrote:
> In our previous episode, Gennadiy Poryev said:
>> I've got two FPC versions installed on my Linux x64 box: 2.6.4 as a 
>> bootstrap and 2.7.1 for building Lazarus. Both were installed through 
>> 'make zipinstall' from svn and untaring to /usr, hence they reside under 
>> /usr/lib64/fpc/2.6.4/ and /usr/lib64/fpc/2.7.1/ accordingly. The 
>> switching is done by force-resymlinking /usr/bin/ppcx64 to the correct 
>> ppcx64 in their corresponding locations so that /usr/bin/fpc may invoke 
>> needed binary. Now Lazarus does not build, complaining about RegisterFCL 
>> and I know this is because of missing fpc.cfg.
>> What is the proper way of generating fpc.cfg in such case? I'm 
>> particularly concerned about how do define 'basepath'. I did that on 
>> Windows easily since bin directory was also located under version 
>> directory, which is not the case in Linux.
> 
> A solution for the ppc* binary is to make a symlink for one of the binaries
> (typically trunk) to ppx64-2.7.1, and to call "fpc" with -P2.7.1 
> 
> This still assumes 2.6.x and 2.7.x can use the same "fpc" binaries, and is
> no solution for the rest.

I'm not up to date on trunk, but so far using the most-recent fpc seems 
compatible with all of 2.2.4 through 2.6.x on multiple native platforms.

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]