[Lazarus] Using different FPC versions

[patspiper]

On 10/02/14 20:09, Mattias Gaertner wrote:
> On Mon, 10 Feb 2014 19:45:44 +0200
> patspiper <patspiper at gmail.com> wrote:
>
>> [...]
>> It allows the caller to specify the location (AFAIK it can be a relative
>> path) of ppcxxx (the actual compiler). That option removes the need to
>> rely on env variables to specify the fpc and ppcxxx paths. It would be
>> enough to provide a qualified path in the IDE options for the fpc
>> executable, and coupled with a -Xp field, it would allow fpc to locate
>> the ppcxxx executable.
>> ex: ./fpc -h -Xp../lib/fpc/2.6.3
> Sorry. I don't get it.
> With this option I can select a ppcxxx executable. But I can
> already select a ppc executable directly. So what do I gain?

You can't specify a ppcxxx executable directly if you cross compile.

>
> And how can I select the right sub tools like fpcres? I still need to
> specify the PATH, don't I?

When a fully qualified path for the fpc executable is specified in the 
IDE options, aren't tools such as fpcres searched for over there?

compiler path: <fullpathtofpc>/fpc
additional switches: -Xp../lib/fpc/$(FPCVER)

The above will allow you to change the path of the fpc executable 
explicitly, and the ppcxxx path follows implicitly due to the -Xp switch.

Stephano