Well,

I think my problem is easier....
when I compile fpc for arm-android target I get ppccrossarm and units
arm-android (with binutils arm-linux-android-*)
 
when I compile fpc for arm-embedded target I get ppccrossarm and units
arm-embedded (with binutils arm-none-eabi-*)

both are able to create binary as I need.

So the last crosschain created overwrites the previous (the ppcrossarm
executable).
Is there a way to instruct  fpc.cfg to use an alternative name (i.e.
ppcrossarmdroid or ppcrossarmembed) when fpc invokes the right compiler?



--
Sent from: http://free-pascal-general.1045716.n5.nabble.com/
_______________________________________________
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Reply via email to