On Mon, May 4, 2009 at 3:31 PM, Jonas Maebe wrote:
> default, a non-cross-compiler indeed generates code for the same
> architecure/OS combination as it was compiled for itself.
Ah, so the compiler could be compiled for x86, but it's target when
compiling applications could be for a different pr
Vincent Snijders schrieb:
> Graeme Geldenhuys schreef:
>> I'm setting up the automated unit test runs for the tiOPF project. I
>> initially ran it only on one Linux server, but now I want to do it on
>> two servers. One being 32bit and the other being 64bit. Once the unit
>> tests are complete, I
On Mon, May 4, 2009 at 3:20 PM, Marco van de Voort wrote:
>
> One is the binary it is itself (S), the other is (T) is what it generates.
> For crosscompilers this differs.
Ah, so it's (S) I'm after. Thanks. :-)
Regards,
- Graeme -
___
fpGUI - a
On 04 May 2009, at 15:18, Graeme Geldenhuys wrote:
What's the difference between these two sets of parameters. Under two
linux systems (32bit and 64bit) both sets of parameters give the same
output. So what's the difference between them?
The host is the architecture/OS for which the compiler
Graeme Geldenhuys schreef:
I'm setting up the automated unit test runs for the tiOPF project. I
initially ran it only on one Linux server, but now I want to do it on
two servers. One being 32bit and the other being 64bit. Once the unit
tests are complete, I use XSLT to generate a newsgroup posti
In our previous episode, Graeme Geldenhuys said:
> What's the difference between these two sets of parameters.
One is the binary it is itself (S), the other is (T) is what it generates.
For crosscompilers this differs.
___
fpc-pascal maillist - fpc-p
