[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

2.4.4.3 Architectures

This project may be built for any of the architectures which are supported by the standard developer tools, as summarized below.

Platform Architectures Tested
MacOS/X ppc ppc
MacOS/X Server 1.0 i386 ppc i386 ppc
OpenStep i386 m68k sparc i386 m68k
NextStep i386 m68k sparc hppa i386 m68k sparc

Crystal Space and the supporting components may be built as multi-architecture binaries (MAB), thus allowing a single executable file to be used on multiple architectures.

When building Crystal Space and its components, multi-architecture binaries are generated by specifying the standard Apple/NeXT makefile variable `TARGET_ARCHS' on the command-line.

By using `TARGET_ARCHS', the desired architectures may be specified during initial configuration of the build system. The chosen architectures are remembered and automatically applied to all subsequent build operations, unless manually overridden. If you do not specify `TARGET_ARCHS' at configuration time, then the project will be compiled for the hardware on which it is being built.

You can also override the configured choice of architectures by specifying `TARGET_ARCHS' for a particular makefile target. For instance, to build the `walktest' demonstration program as a MAB executable for Intel, Motorola, and Sparc, one would type:

 
gnumake TARGET_ARCHS="i386 m68k sparc" walk

When building the supporting libraries (which do not understand Apple/NeXT's `TARGET_ARCHS' makefile variable), multi-architecture binaries are generated by specifying an alternate definition for `CC' on the command-line. For instance, to build the JPEG library for Intel, Motorola, and Sparc one would type:

 
make libjpeg.a CC="cc -arch i386 -arch m68k -arch sparc"

If `CC' is not specified then the library is compiled for the hardware on which it is being built.


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

This document was generated using texi2html