Yann E. MORIN" 5d175195f6 buildtools: move to working directory
There is absolutely *no* reason for the buildtools (wrappers to gcc, g++,
as, ld... for the local machine) to be in the toolchain directory. Moreover,
they are removed after the build completes.

Move them out of the toolchain directory, and into the build directory (but
yet the part specific to the current toolchain). This means we no longer
need to explicitly remove them either, BTW, but we need to save/restore them
for the restart feature.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-12-23 20:43:32 +01:00
2010-11-03 18:36:51 +01:00
2011-01-03 23:40:22 +01:00
2011-01-30 19:25:56 +01:00
2010-10-05 23:25:32 +02:00
2009-06-14 18:19:22 +00:00
2010-10-06 22:54:48 +02:00
2010-08-14 16:37:11 +02:00
2010-08-23 23:24:16 +02:00
2011-01-22 22:52:57 +01:00

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!
Description
A versatile (cross-)toolchain generator.
Readme 20 MiB
Languages
Shell 50.9%
C 27.4%
M4 16.8%
Makefile 2%
Yacc 1.4%
Other 1.5%