[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
33.1 Introduction
We assume that the host- and build-system are not the same, and that
there exists a C cross-compiler CC
running on the build system
producing executables for the host system.
In order to execute programs on the host, it is however not sufficient to simply compile Bigloo-produced programs with this compiler. Indeed, these programs depend on the Bigloo-library which thus has to exist on the host-platform.
Building a cross-compilation environment is done in two phases:
- Build a Bigloo for the build-platform. Usually this is a given.
- Build the Bigloo library for the host-platform. At the same time one might want to build the Bigloo-executable (for the host-platform) too, but this is not a requirement.
Programs can then be cross-compiled simply by telling Bigloo to use the host-library.
Note: if the cross-compiled executable uses shared libraries, then Bigloo’s cross-compiled libraries have to be copied to the host platform. Static executables are self-contained and can be run without modification on the host.
This document was generated on March 31, 2014 using texi2html 5.0.