Difference between revisions of "Cross compilation"
From Organic Design wiki
(the matrix of doom) |
(add in dog food) |
||
| Line 11: | Line 11: | ||
*http://www.airs.com/ian/configure/configure_5.html | *http://www.airs.com/ian/configure/configure_5.html | ||
*[http://kegel.com/crosstool/crosstool-0.42/buildlogs/ gcc toolchain cross compilation matrix] - this guy is keen | *[http://kegel.com/crosstool/crosstool-0.42/buildlogs/ gcc toolchain cross compilation matrix] - this guy is keen | ||
| + | *[[Wikipedia:Eat one's own dog food|Easting one's own dog food]] | ||
[[category:glossary]] | [[category:glossary]] | ||
Revision as of 02:28, 25 July 2006
This means being able to build a binary on a host system that will run on a target system, where these systems are of different architectures. For example compiling the Husk.c under Linux and producing a binary that will run under windows or mac. This is not as simple as it sounds.
- host enviroment
- a version of gcc and binutils that supports cross compilation is required in the host enviroment
- headers to link against are required
- libraries are required to be present that are compatible with the target system.
Related articles
