Yann E. MORIN" ae91413aee scripts/addToolsVersion: properly handle .in vs. .in.2
While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).

Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.

So, for each tool, we need to explicitly know what file to munge.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2012-12-27 12:45:22 +01:00
2012-12-27 00:57:26 +01:00
2012-03-06 21:36:10 +01:00
2012-11-26 11:44:01 +01:00
2012-12-26 19:54:12 +01:00
2012-01-16 23:36:42 +01:00
2009-06-14 18:19:22 +00:00
2012-10-07 23:15:57 +02:00
2012-03-06 21:36:10 +01:00
2011-07-17 16:53:40 +02:00

This is the README for 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:
  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://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%