scripts/build/test_suite.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Jan 01 17:49:44 2012 +0100 (2012-01-01)
changeset 2924 0eab838768b1
permissions -rw-r--r--
cc/gcc: install the core compilers in the build-tools dir

There really is no good reason to install the core compilers in their
own places, one for each pass. We can install them with the other
build tools.

Also, this implies that:
- there are fewer directories to save/restore
- there are fewer symlinks to create for binutils
- the PATH is shorter

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 # Wrapper to build the test suite facilities
     2 #
     3 # Current assumption: test suites are independent of each other
     4 #                     - no order handling required.
     5 
     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}'"
    14         . "${f}"
    15         CT_TEST_SUITE_FACILITY_LIST="${CT_TEST_SUITE_FACILITY_LIST} ${_f}"
    16     else
    17         CT_DoLog DEBUG "Disabling test suite '${_f}'"
    18     fi
    19 done
    20 
    21 # Download the test suite facilities
    22 do_test_suite_get() {
    23     for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
    24         do_test_suite_${f}_get
    25     done
    26 }
    27 
    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
    32     done
    33 }
    34 
    35 # Build the test suite facilities
    36 do_test_suite() {
    37     for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
    38         do_test_suite_${f}_build
    39     done
    40 }
    41