Difference between revisions of "GDC Cross Compiler"
(→Crosstool-NG: Remove outdated information) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 13: | Line 13: | ||
=== Crosstool-NG === | === Crosstool-NG === | ||
| − | The preferred way to build cross compilers is crosstool-NG. Crosstool-NG supports many different architectures and advanced build configurations (e.g. canadian-cross compilers) | + | The preferred way to build cross compilers is crosstool-NG. Crosstool-NG supports many different architectures and advanced build configurations (e.g. canadian-cross compilers). |
See [[GDC/Cross Compiler/crosstool-NG|Cross Compiler/crosstool-NG]] for more information. | See [[GDC/Cross Compiler/crosstool-NG|Cross Compiler/crosstool-NG]] for more information. | ||
Latest revision as of 12:45, 7 June 2015
Building cross compilers is always a tricky task. And building canadian-cross compilers can easily drive you crazy. This page provides an overview of working GDC cross compilers and tutorials on how to build your own.
Contents
Building from source
Existing system root
If you have an existing file system for your target or access to the target via SSH, see GDC/Cross_Compiler/Existing_Sysroot
Crosstool-NG
The preferred way to build cross compilers is crosstool-NG. Crosstool-NG supports many different architectures and advanced build configurations (e.g. canadian-cross compilers).
See Cross Compiler/crosstool-NG for more information.
Making tools step by step
If it is not possible to use crosstools, the toolchain can be made manually step by step. This can also be used to make a native compiler.
See Cross Compiler/Generic for more information.
Bare metal ARM Cortex-M
See Bare Metal ARM Cortex-M GDC Cross Compiler for instructions specific to building a bare metal ARM Cortex-M GDC cross compiler.
