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>
3 ## depends on ! BACKEND
5 ## select LIBELF_TARGET
7 ## help ltrace is a program that simply runs the specified command until it exits.
8 ## help It intercepts and records the dynamic library calls which are called by
9 ## help the executed process and the signals which are received by that process.
10 ## help It can also intercept and print the system calls executed by the program.
14 prompt "ltrace version"
15 # Don't remove next line
16 # CT_INSERT_VERSION_BELOW
21 select LTRACE_0_5_3_or_later
31 # Don't remove next line
32 # CT_INSERT_VERSION_STRING_BELOW
33 default "0.5.3" if LTRACE_V_0_5_3
34 default "0.5.2" if LTRACE_V_0_5_2
36 config LTRACE_0_5_3_or_later