[fpc-devel] FPC and Windows Phone 8
florian at freepascal.org
Mon Mar 24 20:59:33 CET 2014
Am 24.03.2014 20:36, schrieb 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
> bin\arm-linux-androideabi-ld.bfd.exe: cannot find crtbegin_dynamic.o
> 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.
This is normal that fpc builds a compiler for native usage when cross
compiling because it is a test if the cross setup works fine and it
makes also bootstrapping easier. Since I'am not interested in android
development, I've no clue however, how to fix it.
More information about the fpc-devel