Am 09.03.2014 05:12, schrieb peter green:
>
> Cross compiling is a different case, those doing crossbuilds generally
> expect to have to do some manual configuration to get a working
> environment.
We also aim at flawless cross compilation but this works so far only if
the target is windows.
Vsevolod Alekseyev wrote:
Does Free Pascal really treat ARMHF as a separate CPU target,
It didn't when I initally implemented it and from a quick look at the
code it doesn't now. What it does do is a little hacky but it followed
the pattern of what was already done and a cleaner soloution would
From: Michael Van Canneyt
>To: FPC developers' list
>Sent: Saturday, March 8, 2014 2:42 PM
>Subject: Re: [fpc-devel] fpHttpClient heartbeat
>
>
>On Sat, 8 Mar 2014, Leonardo M. Ramé wrote:
>
>> Hi, does anyone know if fpHttpClient has something similar to the HeartBeat
>> option of Synapse?,
On Sat, 8 Mar 2014, Leonardo M. Ramé wrote:
Hi, does anyone know if fpHttpClient has something similar to the HeartBeat
option of Synapse?, this feature is useful for
implementing download progress bars, for example.
It has an onprogress event, this is implemented in trunk.
Michael.___
Hi, does anyone know if fpHttpClient has something similar to the HeartBeat
option of Synapse?, this feature is useful for implementing download progress
bars, for example.
Leonardo M. Ramé
http://leonardorame.blogspot.com___
fpc-devel maillist -
Thanks, that explains.
Mine *is* a cross setup. I'm buiding for Android (and more) on
Windows/Intel.
.
-Original Message-
From: fpc-devel-boun...@lists.freepascal.org
[mailto:fpc-devel-boun...@lists.freepascal.org] On Behalf Of Florian Klampfl
Sent: Saturday, March 08, 2014 11:20 AM
To: F
Am 08.03.2014 16:40, schrieb Vsevolod Alekseyev:
>
> Was this done so that you can have several instances of ARM RTL side
> by side and switch between them seamlessly?
Debian made armhf a separate architecture so we decided to make it a
separate compiler.
> units\armv7-android. In order to build
Does Free Pascal really treat ARMHF as a separate CPU target, distinct from
regular ARM? May I ask why such design? In the grand symphony of native code
generation, the floating point calling convention sounds, to me, as a much
smaller detail than, for example, ARM vs Thumb or PIC vs. non-PIC or
