Difference between revisions of "Cross compilation"
From Organic Design wiki
m |
m (Caretaker: Format cat links) |
||
| Line 1: | Line 1: | ||
| + | [[Category:glossary]] | ||
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. | 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. | ||
| Line 12: | Line 13: | ||
*[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|Eating one's own dog food]] | *[[Wikipedia:Eat one's own dog food|Eating one's own dog food]] | ||
| − | |||
Revision as of 18:41, 28 October 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
