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>
1 This is the README for crosstool-NG
3 Crosstool-NG follows the autoconf dance. So, to get you
4 kick-started, just run:
7 If you are using a development snapshot, you'll have to
8 create the configure script, first. Just run:
11 You will find the documentation in the directory 'docs'.
12 Here is a quick overview of what you'll find there:
15 2 - Installing crosstool-NG
16 3 - Configuring a toolchain
17 4 - Building the toolchain
18 5 - Using the toolchain
26 You can also point your browser at:
27 http://crosstool-ng.org/