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
27 select PPL_NEEDS_FPERMISSIVE
33 # Don't remove next line
34 # CT_INSERT_VERSION_STRING_BELOW
35 default "0.11.2" if PPL_V_0_11_2
36 default "0.11.1" if PPL_V_0_11_1
37 default "0.11" if PPL_V_0_11
38 default "0.10.2" if PPL_V_0_10_2
40 # For PPL 0.10, we need -fpermissive to build on gcc 4.7+
42 config PPL_NEEDS_FPERMISSIVE
45 # For PPL 0.11, we need to pull libpwl if configured static
48 select PPL_NEEDS_LIBPWL if ! COMPLIBS_SHARED
50 config PPL_NEEDS_LIBPWL