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 # Menu for the native GDB
6 depends on ! BARE_METAL
9 Build and install a native gdb for the target, to run on the target.
13 config GDB_NATIVE_STATIC
15 prompt "Build a static native gdb"
17 In case you have trouble with dynamic loading of shared libraries,
18 you will find that a static gdb comes in handy.