1
[subsection {Retargeting The Binaries}]
3
The configuration settings [cmd critcl] uses to drive the compiler,
4
linker, etc. are by default selected based on the platform it is run
5
on, to generate binaries which properly work on this platform.
9
There is one main use-case for overriding this selection, which is
10
done with the option [option -target]:
12
[list_begin enumerated]
14
Cross-compilation. The building of binaries for a platform T
15
while critcl actually runs on platform B.
17
The standard configuration of [cmd critcl] currently has settings for
18
two cross-compilation targets. So, to build 32bit Windows binaries on
19
a Linux host which has the Xmingw cross-compilation development
20
environment installed use
23
critcl -pkg -target mingw32 foo
26
Similarly, building a package for use on ARM processors while critcl
27
is running in an Intel environment use
30
critcl -pkg -target linux-arm foo
33
Note that both configurations assume that the cross-compiling
34
compiler, linke, etc. are found first in the [var PATH].
40
First, to choose among several possible C compiler available on the
41
build host. The standard configuration for most unix platforms uses
42
the platform's native compiler, for example, and