[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The Crystal Space project consists of a number of components and example programs. The following commands are all issued from within the top level Crystal Space source code directory named `CS'.
To begin building Crystal Space, first configure the makefiles for the appropriate platform by typing the correct build command as indicated below.
Platform Build Command MacOS/X gnumake macosx
MacOS/X Server 1.0 gnumake macosxs
OpenStep gnumake openstep
NextStep gnumake nextstep
If you want to build multi-architecture binaries of Crystal Space then you can specify `TARGET_ARCHS' on the configuration command line. Your choice of architectures will be remembered and automatically applied to subsequent build operations. The list of supported architectures varies between MacOS/X, MacOS/X Server 1.0 (Rhapsody), OpenStep, and NextStep. See section 2.4.4.3 Architectures.
For instance, if you want to build Crystal Space executables for Intel, Motorola, and Sparc on an OpenStep 4.2 system, you would configure the makefile system by invoking the following command:
gnumake openstep TARGET_ARCHS="i386 m68k sparc" |
Once the makefiles have been configured for the appropriate platform, you can begin building the Crystal Space demonstration programs. Alternately, if you are interested in building only certain components of the system, such as drivers or libraries, then can do that instead.
To see a list of all targets which can be built, type:
gnumake help |
The simplest way to build the entire package, including all applications, drivers, and plug-in modules is to invoke the makefile target `all':
gnumake -k all |
This can be a fairly time consuming operation. If you would like to be more selective and only build the necessary plug-in modules and a subset of the available applications, you can invoke their targets individually.
For example, to build all plug-in modules, you could invoke this command:
gnumake -k plugins # Builds all plug-in modules. |
Or, for example, you could build only the WalkTest application and the plug-in modules which it most commonly requires.
gnumake walkall # Builds WalkTest and required plug-ins |
For finer control over which applications are built, you can invoke their targets directly. For instance:
gnumake walk # Builds |
All programs require at least some plug-in modules to be present, so be sure to build those as well by invoking the `plugins' makefile target as illustrated above if you have not already invoked the `all' target.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |