[fpc-devel] FPC and Windows Phone 8

[Vsevolod Alekseyev]

Thanks. But the Android build is acting funny now, and I'm not sure why.

make clean all OS_TARGET=android CROSSOPT="-CpARMv7A -CfVFPV3_D16 
-CIthumb" CPU_TARGET=arm INSTALL_PREFIX=C:\FPC\2.7.1

...

C:/FPC/2.7.1/src/compiler/ppcrossarm.exe -Tandroid -Parm 
-XParm-linux-androideabi- -Xr -Ur -Xs -O2 -n -Fuarm -Fusystems 
-FuC:/FPC/2.7.1/src/rtl/units/arm-android -Fiarm -FE. 
-FUarm/units/arm-android -dRELEASE -CpARMv7A -CfVFPV3_D16 -CIthumb -darm 
-dGDB -dBROWSERLOG -Sew -CpARMv7A -CfVFPV3_D16 -CIthumb -darm -dGDB 
-dBROWSERLOG  -Sew pp.pas
D:\android-ndk-r9d\toolchains\arm-linux-androideabi-4.8\prebuilt\windows-x86_64\
bin\arm-linux-androideabi-ld.bfd.exe: cannot find crtbegin_dynamic.o
D:\android-ndk-r9d\toolchains\arm-linux-androideabi-4.8\prebuilt\windows-x86_64\
bin\arm-linux-androideabi-ld.bfd.exe: cannot find -lc
pp.pas(238,36) Error: Error while linking
pp.pas(238,36) Fatal: There were 1 errors compiling module, stopping
Fatal: Compilation aborted

That used to work; the Android cross-toolchain would build without me 
having to provide the path to libc. Why would FPC want to *link* 
anything for Android over the course of cross-toolchain building? I 
thought it would first build a cross-compiler (a Windows executable), 
then compile but not link a bunch of units; no Android-targering linker 
necessary. Now it looks like FPC is trying to build the Android-hosted 
compiler, too.

Removing -CIthumb doesn't help.


On 3/24/2014 3:21 PM, Florian Klämpfl wrote:
> Am 24.03.2014 16:30, schrieb Vsevolod Alek
> Compilation errors encountered with
> make clean all OS_TARGET=linux CROSSOPT="-CpARMv7A -CfVFPV3_D16 -CIthumb
> -al" CPU_TARGET=arm
> are fixed now. However I cannot test the resulting code, as I have no
> suitable armv7a device.
>
> _______________________________________________
> fpc-devel maillist  -  fpc-devel at lists.freepascal.org
> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
>