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>
6 # Parse the tools' paths configuration
7 . "${CT_LIB_DIR}/paths.sh"
9 # We'll need the stdout later, save it
12 # Parse the common functions
13 . "${CT_LIB_DIR}/scripts/functions"
15 # Don't care about any log file
17 rm -f "${tmp_log_file}"
19 # Parse the configuration file
22 # Parse architecture and kernel specific functions
23 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
24 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
29 # All this for this single echo... :-( Sigh, I'll have to re-arrange things...
30 echo "${CT_TARGET}" >&9