mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2024-12-19 12:57:53 +00:00
A versatile (cross-)toolchain generator.
7bfa4139ad
Users tend to look for the build log in the current working directory, rather than in the toolchain's installation dir. While bundling the build log in the toolchain installation dir is nice for distribution and review, it can be easier to have the build log readily available in the working directory, as it is quicker to get to it. So, the build log stays in the working directory until the toolchain is completely and successfully built, and then a (compressed) copy is made. Reported-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> |
||
|---|---|---|
| config | ||
| contrib | ||
| docs | ||
| kconfig | ||
| licenses.d | ||
| patches | ||
| samples | ||
| scripts | ||
| .hgignore | ||
| .hgtags | ||
| .version | ||
| configure | ||
| COPYING | ||
| ct-ng.comp | ||
| ct-ng.in | ||
| LICENSES | ||
| Makefile.in | ||
| README | ||
| steps.mk | ||
| TODO | ||
This is the README for crosstool-NG Crosstool-NG follows the autoconf dance. So, to get you kick-started, just run: ./configure --help 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://ymorin.is-a-geek.org/projects/crosstool Aloha!