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 # Dummy config file to not use a C library *at all*
3 ## depends on BARE_METAL
5 ## help Do not use a C library.
7 ## help This is usefull if your project is self-contained, does not rely on
8 ## help an external C library, and provides all the necessary bits.
10 ## help Most probably usefull to bootloaders, as they generally don't depend
11 ## help on the C library.
13 ## help If unsure: do *not* choose that, and use another option in the choice.