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 # D.U.M.A. - Detect Unintended Memory Access - Memory checker
3 ## depends on ! BACKEND
5 ## help D.U.M.A. - Detect Unintended Memory Access
6 ## help A memory bound checker, with additional features.
7 ## help Formerly known as Electric Fence.
11 prompt "Build a static library"
16 prompt "Build a shared library"
17 default y if SHARED_LIBS
21 prompt "D.U.M.A. version"
22 # Don't remove next line
23 # CT_INSERT_VERSION_BELOW
33 # Don't remove next line
34 # CT_INSERT_VERSION_STRING_BELOW
35 default "2_5_15" if DUMA_V_2_5_15