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 test suite facilities
3 # Current assumption: test suites are independent of each other
4 # - no order handling required.
6 # List all test suite facilities, and parse their scripts
7 CT_TEST_SUITE_FACILITY_LIST=
8 for f in "${CT_LIB_DIR}/scripts/build/test_suite/"*.sh; do
9 _f="$(basename "${f}" .sh)"
10 __f="CT_TEST_SUITE_${_f}"
11 __f=`echo ${__f} | tr "[:lower:]" "[:upper:]"`
12 if [ "${!__f}" = "y" ]; then
13 CT_DoLog DEBUG "Enabling test suite '${_f}'"
15 CT_TEST_SUITE_FACILITY_LIST="${CT_TEST_SUITE_FACILITY_LIST} ${_f}"
17 CT_DoLog DEBUG "Disabling test suite '${_f}'"
21 # Download the test suite facilities
23 for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
24 do_test_suite_${f}_get
28 # Extract and patch the test suite facilities
29 do_test_suite_extract() {
30 for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
31 do_test_suite_${f}_extract
35 # Build the test suite facilities
37 for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
38 do_test_suite_${f}_build