Yann E. MORIN" 7bfa4139ad scripts: leave changelog in build dir, copy to install dir
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>
2011-03-20 00:02:21 +01:00
2011-03-19 22:24:29 +01:00
2010-11-03 18:36:51 +01:00
2011-02-27 15:27:54 +01:00
2011-01-03 23:40:22 +01:00
2011-03-14 22:16:01 +01:00
2009-06-14 18:19:22 +00: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.9%
Makefile 1.9%
Yacc 1.4%
Other 1.5%