> At least after removing -mfloat-abi=hard it compiles through here.
> (make clean crosszipinstall OS_TARGET=android CPU_TARGET=arm
> CROSSOPT="-Cfvfpv3 -mfloat-abi=soft -Cparmv7" FPC=i386-linux-ppc386
> BINUTILSPREFIX=arm-linux-androideabi-)
Does not compile on windows, though. What are you usin
Hi,
On Thu, 2012-08-02 at 09:36 +0200, Dennis Spreen wrote:
> > At least after removing -mfloat-abi=hard it compiles through here.
> > (make clean crosszipinstall OS_TARGET=android CPU_TARGET=arm
> > CROSSOPT="-Cfvfpv3 -mfloat-abi=soft -Cparmv7" FPC=i386-linux-ppc386
> > BINUTILSPREFIX=arm-linux-
> At least after removing -mfloat-abi=hard it compiles through here.
> (make clean crosszipinstall OS_TARGET=android CPU_TARGET=arm
> CROSSOPT="-Cfvfpv3 -mfloat-abi=soft -Cparmv7" FPC=i386-linux-ppc386
> BINUTILSPREFIX=arm-linux-androideabi-)
Does not compile on windows, though. What are you usin
Thomas Schatzl wrote:
Last time I tried compiling with -Cfvfpv2 or 3 the compiler did not
cycle, so I could not test further. Has been some time, and this was
native compilation.
Last I heard cycling goes fine but FPU options don't get passed down
to other parts of the build process leading t
Hi,
On Tue, 2012-07-31 at 14:20 +0200, Dennis Spreen wrote:
> I've tested the "new" targetandroid branch, and by using fpc 2.6.0 and
> making a new fpcmake (taken from the targetandroid branch), I'm able to
> compile for armv5:
>
> make crossinstall OS_TARGET=android CPU_TARGET=arm CROSSOPT="-CfS
I've tested the "new" targetandroid branch, and by using fpc 2.6.0 and
making a new fpcmake (taken from the targetandroid branch), I'm able to
compile for armv5:
make crossinstall OS_TARGET=android CPU_TARGET=arm CROSSOPT="-CfSOFT
-Cparmv5t -mfloat-abi=soft" CROSSBINDIR=%ANDROID_BIN_ARM%
BINUTILSP
