On 10/02/14 20:24, Sven Barth wrote:
On 10.02.2014 19:20, patspiper wrote:
On 10/02/14 20:09, Mattias Gaertner wrote:
On Mon, 10 Feb 2014 19:45:44 +0200
patspiper <patspi...@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.
Of course I can. I just need to specify the right ppcXXX executable.
I didn't mean it is not possible, but it is a hassle. You'll have to
select at least the right ppcxxx and the right widgetset. Whereas if you
specify the fpc executable, you can, with a single click, change targets
(using build modes).
Stephano
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
