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 companion tools facilities
3 # List all companion tools facilities, and parse their scripts
4 CT_COMP_TOOLS_FACILITY_LIST=
5 for f in "${CT_LIB_DIR}/scripts/build/companion_tools/"*.sh; do
6 _f="$(basename "${f}" .sh)"
8 __f="CT_COMP_TOOLS_${_f}"
9 if [ "${!__f}" = "y" ]; then
10 CT_DoLog DEBUG "Enabling companion tools '${_f}'"
12 CT_COMP_TOOLS_FACILITY_LIST="${CT_COMP_TOOLS_FACILITY_LIST} ${_f}"
14 CT_DoLog DEBUG "Disabling companion tools '${_f}'"
18 # Download the companion tools facilities
19 do_companion_tools_get() {
20 for f in ${CT_COMP_TOOLS_FACILITY_LIST}; do
21 do_companion_tools_${f}_get
25 # Extract and patch the companion tools facilities
26 do_companion_tools_extract() {
27 for f in ${CT_COMP_TOOLS_FACILITY_LIST}; do
28 do_companion_tools_${f}_extract
32 # Build the companion tools facilities
33 do_companion_tools() {
34 for f in ${CT_COMP_TOOLS_FACILITY_LIST}; do
35 do_companion_tools_${f}_build