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 libs facilities
3 # List all companion tools facilities, and parse their scripts
4 CT_COMP_LIBS_FACILITY_LIST=
5 for f in "${CT_LIB_DIR}/scripts/build/companion_libs/"*.sh; do
6 _f="$(basename "${f}" .sh)"
9 CT_COMP_LIBS_FACILITY_LIST="${CT_COMP_LIBS_FACILITY_LIST} ${_f}"
12 # Download the companion libs facilities
13 do_companion_libs_get() {
14 for f in ${CT_COMP_LIBS_FACILITY_LIST}; do
19 # Extract and patch the companion libs facilities
20 do_companion_libs_extract() {
21 for f in ${CT_COMP_LIBS_FACILITY_LIST}; do
26 # Build the companion libs facilities for build
27 do_companion_libs_for_build() {
28 for f in ${CT_COMP_LIBS_FACILITY_LIST}; do
33 # Build the companion libs facilities for host
34 do_companion_libs_for_host() {
35 for f in ${CT_COMP_LIBS_FACILITY_LIST}; do