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 # ARM specific configuration file
3 ## select ARCH_SUPPORTS_32
4 ## select ARCH_DEFAULT_32
5 ## select ARCH_SUPPORTS_BOTH_MMU
6 ## select ARCH_DEFAULT_HAS_MMU
7 ## select ARCH_SUPPORTS_BOTH_ENDIAN
8 ## select ARCH_DEFAULT_LE
9 ## select ARCH_SUPPORTS_WITH_ARCH
10 ## select ARCH_SUPPORTS_WITH_CPU
11 ## select ARCH_SUPPORTS_WITH_TUNE
12 ## select ARCH_SUPPORTS_WITH_FLOAT
13 ## select ARCH_SUPPORTS_WITH_FPU
14 ## select ARCH_SUPPORTS_SOFTFP
16 ## help The ARM architecture, as defined by:
17 ## help http://www.arm.com/