mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2025-04-23 18:33:37 +00:00
33cdb19ed5
In case we build a baremetal compiler, use the standard passes: - core_cc is used to build the C library; - as such, it is meant to run on build, not host; - the final compiler is meant to run on host; As the current final compiler step can not build a baremetal compiler, call the core backend from the final step. NB: Currently, newlib is built during the start_files pass, so we have to have a core compiler by then... Once we can build the baremetal compiler from the final cc step, then we can move the newlib build to the proper step, and then get rid of the core pass-1 static compiler... Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
This is the README for crosstool-NG
Crosstool-NG follows the autoconf dance. So, to get you
kick-started, just run:
./configure --help
If you are using a development snapshot, you'll have to
create the configure script, first. Just run:
./bootstrap
You will find the documentation in the directory 'docs'.
Here is a quick overview of what you'll find there:
0 - Table of content
1 - Introduction
2 - Installing crosstool-NG
3 - Configuring a toolchain
4 - Building the toolchain
5 - Using the toolchain
6 - Toolchain types
7 - Contributing
8 - Internals
A - Credits
B - Known issues
C - Misc. tutorials
You can also point your browser at:
http://crosstool-ng.org/
Aloha!