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
Am 31.07.2012 22:40, schrieb Craig Peterson:
Hi Sven,
On 7/31/2012 3:11 PM, Sven Barth wrote:
Delphi does not use the "@" to designate the function address, so this
isn't to take the address of a function/method. In Delphi you just use
"r" (in your example).
Normally Delphi doesn't allow assi
Hi,
On Wed, 2012-08-01 at 09:38 +0200, Thomas Schatzl wrote:
> Hi,
>
> On Tue, 2012-07-31 at 14:20 +0200, Dennis Spreen wrote:
> > Thomas wrote:
> > But one has to specifiy OS_TARGET=linux instead of OS_TARGET=android?
> > Is this correct?
>
> No, OS_TARGET=android should be specified, although
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
Hi,
On Tue, 2012-07-31 at 14:20 +0200, Dennis Spreen wrote:
> Thomas wrote:
> "Note that if you want to try, some time ago android/x86 compiler
> support has been added (must add -Cfsse3 though to get valid
> executables)."
>
> But one has to specifiy OS_TARGET=linux instead of OS_TARGET=android?
