Note that you probably don't need two different cross compilers
if your cpu-OS target is the same
Target CPU family is same: "arm", but Target processor is not the
same: "ARMv4" versus "ARMv7" ...
So I do not know if this requires two pre-compiled cross-compilers
or not?
You only need different compilers if you have different ABIs (e.g.
Soft Float vs. Hard Float). For WinCE that isn't applicable however.
So it does not matter how I build cross-compiler using FpcUpDeluxe:
wheter I use "-Cparmv5" or "-Cparmv7A" ?
Then there is still problem with precompiled RTL/packages?
Because when I only change "Target processor" (in Lazarus build using
FpcUpDeluxe) I can compile application, but I can not run it on target
system (so I guess, that resulting EXE is not compiled for target
processor).
When I add to Custom options: -CfVFPV2 then I get error while compiling:
Fatal: Can't find unit system used by Test1
When I download and install default Lazarus and cross-compiler then when
I change "Target processor" to "ARMv5" or "ARMv7A" I get:
"project1.lpr(22,0) Error: Error while assembling exitcode 1"
-Laco.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
