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

[patspiper]

On 17/02/14 18:26, Tomas Hajny wrote:
> On Mon, February 17, 2014 16:13, Michael Van Canneyt wrote:
>> On Mon, 17 Feb 2014, patspiper wrote:
>>> On 17/02/14 16:45, Mattias Gaertner wrote:
>>>> On Mon, 17 Feb 2014 15:10:03 +0100 (CET)
>>>> Michael Van Canneyt <michael at freepascal.org> wrote:
>>>>
>>>>> On Mon, 17 Feb 2014, Mattias Gaertner wrote:
>>>>> [...]
>>>>>> Is there already a doc about how to install multiple versions of fpc?
>>>>> No, because
>>>>> a) There are so many ways to do it
>>>>> b) There are so many platforms.
>>>>> I prefer to document the possibilities and let the user figure out for
>>>>> himself what works best.
>>>> That's definitely a good thing.
>>>>
>>>> The next step would be to create an example. I guess a common setup is
>>>> the latest release and trunk.
>>>>
>>>> Let's say I start such a page.
>>>>
>>>> Then I would explain the two common setups
>>>>
>>>> The clean approach:
>>>> 1.1. read Michael's docs
>>>> 1.2. install the latest released compiler
>>>> 1.3. download the trunk sources, compile it
>>>> 1.4. "make install INSTALL_PREFIX=~/fpc/2.7.1"
>>>> 1.5. setup a fpc.cfg (~/fpc/2.7.1/lib/etc/fpc.cfg), add
>>>> -FD~/fpc/2.7.1/bin and adapt the -Fu lines.
>>>>
>>>> Then you can select the 2.6.2 via /usr/bin/fpc or the 2.7.1 via
>>>> ~/fpc/2.7.1/lib/2.7.1/ppcx86.
>>> Calling ppcxxx directly breaks easy cross compilation using build modes.
>> Not if the IDE is aware of this.
> Indeed - the IDE doesn't need to call ppcx86 directly, but it can simply
> pass ~/fpc/2.7.1/lib/2.7.1/ to fpc via -Xp and let it do its job (it
> should also call fpc from ~/fpc/2.7.1/lib/2.7.1/ in such a case to cater
> for situations like support of a new platform support not available with
> the latest released version).

I suggested that Lazarus has for every fpc version the following info:

- Path to fpc
- Path to ppc
- Tools path (optional)

It could then use:
<pathtofpc>fpc -Xp<pathtoppc> -FD<pathtotools>
with the -FD part being optional

Stephano