On Mon, May 4, 2009 at 3:31 PM, Jonas Maebe <jonas.ma...@elis.ugent.be> 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 processor. Cool! I
only new the -T parameter.
> Do you mean whether the compiler binary itself is 32 or 64 bit? There is no
Yes.
> the compiler. I'm not sure what the use for this information could be
> though.
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 posting looking
similar to the following (see below). The variables will be filled in
before posting to the NNTP server. So in the posting I want to mention
what FPC version was used and if it was a 32bit or 64bit compiler.
============================
tiOPF2 - FPCUnit Results
------------------------
SVN revision:
r#REV
Build time:
<datetime>
Elapsed time:
<elapsedtime>
Summary:
FPC #FPCVER (#FPCCPU) - Tests run: %d, Failures: %d, Errors: %d
[...snip...]
============================
Regards,
- Graeme -
_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
