Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2010-05

benefit of "cross" string added to compiler name?

3 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Thierry Bothorel

Hi,

I am not comfortable with make and I was looking for why i get for example "ppcrossarm" if I cross build with a "one line" like

make clean all install CROSSINSTALL=1 .......

and only "pparm" with

make clean all .......
make install CROSSINSTALL=1 .......

Reading makefile I understood why, now I wonder what is the benefit to add the "cross" string inside the compiler file name ? ... Is this really needed?

Thierry B.

Jonas Maebe
to Thierry Bothorel
Thierry Bothorel wrote
Reading makefile I understood why, now I wonder what is the benefit to add the "cross" string inside the compiler file name ?

When you build the entire source tree for a different architecture than the host architecture, both a cross-compiler and a native compiler are created. Both binaries are in fpc/compiler, so they have to have different names.

Jonas

Jonas Maebe
Thierry Bothorel wrote 9 lines
Jonas Maebe a écrit : > When you build the entire source tree for a different architecture than the host architecture, both a cross-compiler and a native compiler are created. Both binaries are in fpc/compiler, so they have to have different names. for my personal need, I just use http://svn.freepascal.org/svn/fpcbuild/trunk/install/cross/buildcrosssnaphot script to build my specific target cpu / target OS cross compiler only, and I have no previous "ppcarm" file. So in my case it does not matter what the file name is? (This script does not add the 'cross' string).

It mainly matters if you use the "fpc" binary (or in general, any fpc or fpcmake-based makefiles), because than the "cross" will automatically be added to the name of the compiler binary when cross-compiling.

Jonas