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>
6 # Don't remove next line
7 # CT_INSERT_VERSION_BELOW
37 # Don't remove next line
38 # CT_INSERT_VERSION_STRING_BELOW
39 default "3.1.0" if MPFR_V_3_1_0
40 default "3.0.1" if MPFR_V_3_0_1
41 default "3.0.0" if MPFR_V_3_0_0
42 default "2.4.2" if MPFR_V_2_4_2
43 default "2.4.1" if MPFR_V_2_4_1
44 default "2.4.0" if MPFR_V_2_4_0