On 10/02/14 19:38, Michael Van Canneyt wrote:
On Mon, 10 Feb 2014, patspiper wrote:
On 10/02/14 19:12, Michael Van Canneyt wrote:
On Mon, 10 Feb 2014, patspiper wrote:
Once this is implemented, it can be done by "additions and
overrides" too.
Although it is a welcome feature, it will make the usage really
complicated considering build modes might cater for debug/release,
FPC version, win/linux, etc...
I instead propose to have a field next to the compiler path in the
IDE options that accepts fpc's -Xp parameter. Xp allows one to
specify the relative folder of the actual compiler (ppcxxx) with
respect to the fpc executable. That would work well since each
ppcxxx's location is fixed with respect to its associated fpc
executable.
That assumption is not correct on Unix.
That's interesting and unexpected. Can you give an example on fpc's
folder hierarchy on unix?
Well:
fpc is in /usr/local/bin/fpc
various compilers are in /usr/local/lib/fpc/$version/ppcXXX
or (depending on how it was installed):
/usr/bin/fpc
and
/usr/lib/fpc/$version/ppcXXX
Same paths are used on Darwin.
Great! You can use -Xp../lib/fpc/$(FPCVER) in both cases, and hence it
is a fixed relative path (considering the $FPCVER macro).
Stephano
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
