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 # Wrapper to build the debug facilities
3 # List all debug facilities, and parse their scripts
4 CT_DEBUG_FACILITY_LIST=
5 for f in "${CT_LIB_DIR}/scripts/build/debug/"*.sh; do
6 _f="$(basename "${f}" .sh)"
9 if [ "${!__f}" = "y" ]; then
10 CT_DoLog DEBUG "Enabling debug '${_f}'"
12 CT_DEBUG_FACILITY_LIST="${CT_DEBUG_FACILITY_LIST} ${_f}"
14 CT_DoLog DEBUG "Disabling debug '${_f}'"
18 # Download the debug facilities
20 for f in ${CT_DEBUG_FACILITY_LIST}; do
25 # Extract and patch the debug facilities
27 for f in ${CT_DEBUG_FACILITY_LIST}; do
32 # Build the debug facilities
34 for f in ${CT_DEBUG_FACILITY_LIST}; do