Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
config/test_suite.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Mar 20 00:02:21 2011 +0100 (2011-03-20)
changeset 2339 730e2d63296b
child 2484 d1a8c2ae7946
permissions -rw-r--r--
scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     1 # Test suite config options

     2 

     3 if EXPERIMENTAL

     4 

     5 menu "Test suite"

     6 

     7 config TEST_SUITE

     8     bool

     9     default n

    10 

    11 config TEST_SUITE_GCC

    12     bool

    13     prompt "GCC test suite"

    14     depends on EXPERIMENTAL

    15     default n

    16     select TEST_SUITE

    17     help

    18       Select this option to install the GCC test suite in $CT_PREFIX_DIR/test_suite.

    19 

    20       The GCC test suite includes a collection of various toolchain tests for GCC -

    21       it utilizes the DejaGnu test framework.

    22 

    23       For some tests a network enabled target with ssh server is required.

    24 

    25       A helper Makefile is provided for running the tests - please see the included 

    26       README for information on how to run the test suite.

    27 

    28 endmenu

    29 

    30 endif
crosstool-ng