Bryan Hundven 6f8e89cb5c consistency: Use exported variables of required tools
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>
2015-11-17 02:48:09 -08:00
2015-11-13 10:24:22 -08:00

Crosstool-NG Build Status

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:

  1. Table of content
  2. Introduction
  3. Installing crosstool-NG
  4. Configuring a toolchain
  5. Building the toolchain
  6. Using the toolchain
  7. Toolchain types
  8. Contributing
  9. Internals
  1. Credits
  2. Known issues
  3. Misc. tutorials

You can also point your browser at: http://crosstool-ng.org

Aloha!

Description
A versatile (cross-)toolchain generator.
Readme 20 MiB
Languages
Shell 50.9%
C 27.4%
M4 16.9%
Makefile 1.9%
Yacc 1.4%
Other 1.5%