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 # This file adds the functions to build the GCC test suite
2 # Copyright 2010 DoréDevelopment
3 # Created by Martin Lund <mgl@doredevelopment.dk>
4 # Licensed under the GPL v2. See COPYING in the root of this package
6 do_test_suite_gcc_get() { :; }
7 do_test_suite_gcc_extract() { :; }
8 do_test_suite_gcc_build() { :; }
10 # Overide functions depending on configuration
11 if [ "${CT_TEST_SUITE_GCC}" = "y" ]; then
13 do_test_suite_gcc_build() {
15 CT_DoStep INFO "Installing GCC test suite"
17 CT_DoExecLog ALL mkdir -p "${CT_TEST_SUITE_DIR}/gcc"
18 CT_DoExecLog ALL cp -av "${CT_LIB_DIR}/contrib/gcc-test-suite/default.cfg" \
19 "${CT_LIB_DIR}/contrib/gcc-test-suite/Makefile" \
20 "${CT_LIB_DIR}/contrib/gcc-test-suite/README" \
21 "${CT_SRC_DIR}/gcc-${CT_CC_VERSION}/gcc/testsuite" \
22 "${CT_TEST_SUITE_DIR}/gcc"
24 CT_DoExecLog ALL sed -i -r -e "s/@@DG_TARGET@@/${CT_TARGET}/g;" \
25 "${CT_TEST_SUITE_DIR}/gcc/Makefile"
30 fi # CT_TEST_SUITE_GCC