crosstool-ng/config/config.in

mainmenu "crosstool-NG $(CT_VERSION) Configuration"
source "config/configure.in"
source "config/global.in"
source "config/target.in"
source "config/toolchain.in"
source "config/kernel.in"
source "config/binutils.in"
source "config/libc.in"
source "config/cc.in"
source "config/debug.in"
source "config/comp_libs.in"
source "config/comp_tools.in"
source "config/test_suite.in"
config: Update environment variable usage Upstream changes in the way kconfig handles environment variables means we need to update our usage of them. Signed-off-by: Chris Packham <judge.packham@gmail.com> 2020-12-09 21:42:54 +13:00			`mainmenu "crosstool-NG $(CT_VERSION) Configuration"`
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/global.in"`
			`source "config/target.in"`
			`source "config/toolchain.in"`
			`source "config/kernel.in"`
			`source "config/binutils.in"`
			`source "config/libc.in"`
config: switch cc with libc in the config order Some of the compiler options depend on the C library choice, (e.g. whether core passes are needed). Since the compiler menu comes before the C library menu, those options may or may not be visible until the C library is chosen, leading to either options being visible by the user (thus be puzzling as they would not apply to his case), or invisible to him (yet again puzzling him). Invert the order of the compiler and the C library in the menuconfig. It anyway looks more rational, in the end. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> 2014-05-11 13:38:12 +02:00			`source "config/cc.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/debug.in"`
Switch gen-kconfig to new framework Also: - Move companion_* to comp_* to match the kconfig symbols - Replace bootstrap with former gen-versions.sh - Fold .in.2 into their respective first parts; this moves common options to the end - if it is undesirable, inclusion of .in can be moved where *.in.2 used to be (but that will also move version selection after common options). - Retire addToolVersion.sh (may later replace with a more comprehensive script that tries to download the added tarballs, copy the patches and try to apply them, and create a version.desc). Signed-off-by: Alexey Neyman <stilor@att.net> 2017-07-04 19:19:42 -07:00			`source "config/comp_libs.in"`
			`source "config/comp_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"`