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 # Companion tools config options
7 comment "READ HELP before you say 'Y' below !!!"
10 prompt "Build some companion tools"
12 Crosstool-NG relies on some external tools to be recent enough, namely:
13 make = 3.81 (in some cases)
19 If your system has older versions, we can build them for you,
20 but you are strongly encouraged to update your system instead!
24 config COMP_TOOLS_make
32 config COMP_TOOLS_autoconf
36 config COMP_TOOLS_automake
40 config COMP_TOOLS_libtool