crosstool-ng/config/config.in

mainmenu "The crosstool-NG configuration menu"
source "config/configure.in"
source "config/backend.in"
source "config/global.in"
source "config/target.in"
source "config/toolchain.in"
source "config/kernel.in"
source "config/binutils.in"
source "config/cc.in"
source "config/libc.in"
source "config/debug.in"
source "config/companion_libs.in"
source "config/companion_tools.in"
source "config/test_suite.in"
config: add main menu title Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 2011-05-10 23:56:11 +02:00			`mainmenu "The crosstool-NG configuration menu"`
configure: add possibility to set arbitrary variable in check_for If check_for is able to find the required prog/inc/lib, allow it to set an arbitrary variable to 'y'. This variable is then pushed down to the kconfig definition. For example: has_or_abort prog=foobar kconfig=has_foobar If foobar is available, it yields a kconfig variable defaulting to y: config CONFIGURE_has_foobar bool default y If foobar is missing, it yields a kconfig variable defaulting to n: config CONFIGURE_has_foobar bool Thus it is possible to depends on that variabel to show/hide options: config SOME_FEATURE bool prompt "Some feature" depends on CONFIGURE_has_foobar Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 2011-05-26 22:51:03 +02:00			`source "config/configure.in"`
config: fix style issues when source-ing files Always enclose the sourced file between double-quotes (purely for consistency; enclosing or not are both allowed by the kconfig language). 2010-03-29 20:24:50 +02:00			`source "config/backend.in"`
			`source "config/global.in"`
			`source "config/target.in"`
			`source "config/toolchain.in"`
			`source "config/kernel.in"`
			`source "config/binutils.in"`
			`source "config/cc.in"`
			`source "config/libc.in"`
			`source "config/debug.in"`
			`source "config/companion_libs.in"`
			`source "config/companion_tools.in"`
test-suite: Added new test suite feature (experimental) This patch adds support for installing the gcc test suite. A helper Makefile is provided for building and running the gcc tests. The default configuration runs all gcc tests and requires automatic ssh/scp login access to a networked target board. See README for more details. Note: Current feature is tested with the powerpc-unknown-linux-gnu sample but it should work with others as well. Signed-off-by: Martin Lund <mgl@doredevelopment.dk> 2010-05-19 17:53:04 +02:00			`source "config/test_suite.in"`