In our previous episode, Marco van de Voort said:
> > > fpc -Parm calls ppcarm, fpc -Px86_64 calls ppcx64.
> >
> > Besides the language - fpc and lazarus are so cool tools!
>
> and fpc -V-1.0 calls ppc386-1.0 etc etc :-)
Whoops, that should be -V1.0 of course. The idea is that you can give
rel
In our previous episode, Marc Santhoff said:
> > fpc -Parm calls ppcarm, fpc -Px86_64 calls ppcx64.
>
> Besides the language - fpc and lazarus are so cool tools!
and fpc -V-1.0 calls ppc386-1.0 etc etc :-)
___
fpc-pascal maillist - fpc-pascal@lists.
On Fr, 2017-11-10 at 19:07 +0100, Mattias Gaertner wrote:
> On Fri, 10 Nov 2017 18:57:19 +0100
> Marc Santhoff wrote:
>
> >[...]
> > > You can either use fpc and switch the target OS and /or processor.
> >
> > That solution isnt't doable, that would require a compiler for X86_64
> > and ARM.
>
Am 10.11.2017 18:59 schrieb "Marc Santhoff" :
On Fr, 2017-11-10 at 18:22 +0100, Karoly Balogh (Charlie/SGR) wrote:
> Hi,
>
> On Fri, 10 Nov 2017, Marc Santhoff wrote:
>
> > What is that, is ppc used for bootstrapping the cross compiler
> > regardless of any other fpc maybe installed?
>
> Yes. Firs
On Fri, 10 Nov 2017 18:57:19 +0100
Marc Santhoff wrote:
>[...]
> > You can either use fpc and switch the target OS and /or processor.
>
> That solution isnt't doable, that would require a compiler for X86_64
> and ARM.
fpc -Parm calls ppcarm, fpc -Px86_64 calls ppcx64.
Mattias
__
On Fr, 2017-11-10 at 18:22 +0100, Karoly Balogh (Charlie/SGR) wrote:
> Hi,
>
> On Fri, 10 Nov 2017, Marc Santhoff wrote:
>
> > What is that, is ppc used for bootstrapping the cross compiler
> > regardless of any other fpc maybe installed?
>
> Yes. First that ppc gets built with the "other FPC" i
On Fr, 2017-11-10 at 18:25 +0100, Mattias Gaertner wrote:
> On Fri, 10 Nov 2017 17:47:11 +0100
> Marc Santhoff wrote:
>
> > Hi again,
> >
> > (too many sub threads, answering here - thanks to all helpers!)
> >
> > OK, "$FPC -va | grep CPU" does the trick. If using the ppcrossarm:
> >
> > marc@
On Fri, 10 Nov 2017 17:47:11 +0100
Marc Santhoff wrote:
> Hi again,
>
> (too many sub threads, answering here - thanks to all helpers!)
>
> OK, "$FPC -va | grep CPU" does the trick. If using the ppcrossarm:
>
> marc@puma:/home/marc/program/fpc-cross/src/fpc/compiler > ./ppcrossarm
> -va|grep
Hi,
On Fri, 10 Nov 2017, Marc Santhoff wrote:
> What is that, is ppc used for bootstrapping the cross compiler
> regardless of any other fpc maybe installed?
Yes. First that ppc gets built with the "other FPC" installed. Or you can
specify a startup compiler explicitly with FPC= argument to the
Hi again,
(too many sub threads, answering here - thanks to all helpers!)
OK, "$FPC -va | grep CPU" does the trick. If using the ppcrossarm:
marc@puma:/home/marc/program/fpc-cross/src/fpc/compiler > ./ppcrossarm -va|grep
CPU
[0.004] Macro defined: CPUARMEL
[0.004] Macro defined: FPC_CPUCROSSCOM
In our previous episode, Marc Santhoff said:
> > #ENDIF
>
> I see, so when using fpc for ARM these define is automatically set?
> And would that be CPUAVR for Atmels chips?
(easiest is to just fpc -va some dummy source and then grep for CPU, or look
in the compiler sources (options.pas or systems
> When I'm in doubt
about the conditional defines, I either google or take advantage of
Lazarus: in project->options I select the target CPU family and the
target processor, and then I use "show all options" to see which defines
are set.
fpc -vc is your friend here.
--
Sent from: http://fr
Il 09/11/2017 22:56, Marc Santhoff ha scritto:
I see, so when using fpc for ARM these define is automatically set?
Yes
And would that be CPUAVR for Atmels chips?
Not sure about that. I never used fpc on Atmel chips. When I'm in doubt
about the conditional defines, I either google or take adva
On Do, 2017-11-09 at 21:31 +0100, Giuliano Colla wrote:
> Il 09/11/2017 02:36, Marc Santhoff ha scritto:
>
> > how does fpc and it's makefiles handle the case of installing a cross
> > compiler on a system having fpc installed?
> >
> > The target path will differ and I can set that, but how is the
Il 09/11/2017 02:36, Marc Santhoff ha scritto:
how does fpc and it's makefiles handle the case of installing a cross
compiler on a system having fpc installed?
The target path will differ and I can set that, but how is the config
file .fpc.cfg handled?
You may edit your fpc.cfg for your diffe
On Do, 2017-11-09 at 20:05 +0200, Christo wrote:
> On Thu, 2017-11-09 at 02:36 +0100, Marc Santhoff wrote:
> > Additionally there seems to be no compiler switch for changing the
> > configuration file to use, only -n for ignoring it. Is ist possible
> > to
> > name the .cfg on the command line or h
On Thu, 2017-11-09 at 02:36 +0100, Marc Santhoff wrote:
> Additionally there seems to be no compiler switch for changing the
> configuration file to use, only -n for ignoring it. Is ist possible
> to
> name the .cfg on the command line or how would it be done better?
Yes, specify alternative confi
17 matches
Mail list logo
