mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2025-04-10 12:49:55 +00:00
We check for apps: * make * sed * grep * awk * libtool/libtoolize * install * patch * and more ...during configure. Our scripts should be consistent about using the variables that define where the found tool was found. Of course, we do hard-link these tools in buildtools, but that should be a backup for the components we are building. Our scripts should always use the tools we find. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Rename directory "licenses" to "licenses.d" for those filesystems unable to handle lower/upper case.
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:
- Table of content
- Introduction
- Installing crosstool-NG
- Configuring a toolchain
- Building the toolchain
- Using the toolchain
- Toolchain types
- Contributing
- Internals
- Credits
- Known issues
- Misc. tutorials
You can also point your browser at: http://crosstool-ng.org
Aloha!
Description
Languages
Shell
50.9%
C
27.4%
M4
16.8%
Makefile
2%
Yacc
1.4%
Other
1.5%