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 # MIPS specific config options
12 This is the -mabi=32 gcc option.
19 This is the -mabi=n32 gcc option.
26 This is the -mabi=64 gcc option.
28 # Not supported on Linux:
29 # o64 : seems related to *BSD
30 # eabi : seems related to bare-metal
36 default "32" if ARCH_mips_o32
37 default "n32" if ARCH_mips_n32
38 default "64" if ARCH_mips_n64