config/test_suite.in
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Dec 27 12:45:22 2012 +0100 (2012-12-27)
changeset 3152 b286c7993be5
parent 2484 d1a8c2ae7946
permissions -rw-r--r--
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>
mgl@1965
     1
# Test suite config options
mgl@1965
     2
mgl@1965
     3
if EXPERIMENTAL
mgl@1965
     4
mgl@1965
     5
menu "Test suite"
mgl@1965
     6
mgl@1965
     7
config TEST_SUITE
mgl@1965
     8
    bool
mgl@1965
     9
mgl@1965
    10
config TEST_SUITE_GCC
mgl@1965
    11
    bool
mgl@1965
    12
    prompt "GCC test suite"
mgl@1965
    13
    select TEST_SUITE
mgl@1965
    14
    help
mgl@1965
    15
      Select this option to install the GCC test suite in $CT_PREFIX_DIR/test_suite.
mgl@1965
    16
mgl@1965
    17
      The GCC test suite includes a collection of various toolchain tests for GCC -
mgl@1965
    18
      it utilizes the DejaGnu test framework.
mgl@1965
    19
mgl@1965
    20
      For some tests a network enabled target with ssh server is required.
mgl@1965
    21
benoit@2484
    22
      A helper Makefile is provided for running the tests - please see the included
mgl@1965
    23
      README for information on how to run the test suite.
mgl@1965
    24
mgl@1965
    25
endmenu
mgl@1965
    26
mgl@1965
    27
endif