NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
45166f30dc
kumquat-buildroot/toolchain/Config.in

44 lines
1.2 KiB
Plaintext
Raw Normal View History

- Subsume and collaps toolchain options in one menu This is ment to ease configuration by providing toolchain related options in one place No functional changes, just shuffling the menus around..
2007-09-22 16:16:25 +02:00
menu "Toolchain"
Support building using an external toolchain. Questions to the mailing list and all other comments to <biteme@devnull.com>.
2007-02-06 19:19:38 +01:00
choice
prompt "Toolchain type"
Add BR2_CROSS_TOOLCHAIN_TARGET_UTILS to allow bundling of some useful debug apps with a deployed cross toolchain. Should probably do ltrace as well... Also, add another compat symlink for cross gdb.
2005-08-04 05:49:25 +02:00
help
- revert some bad checkins, fixup bad settings in atmel targets and move the gcc target abi back to a place where the other arch-specific settings live
2007-09-26 23:12:38 +02:00
Select whether to use the toolchain provided by buildroot
or an external toolchain.
Some vendors provide toolchains in binary form, some in
source form.
- add more help text
2007-09-26 00:03:18 +02:00
Support building using an external toolchain. Questions to the mailing list and all other comments to <biteme@devnull.com>.
2007-02-06 19:19:38 +01:00
config BR2_TOOLCHAIN_BUILDROOT
- Subsume and collaps toolchain options in one menu This is ment to ease configuration by providing toolchain related options in one place No functional changes, just shuffling the menus around..
2007-09-22 16:16:25 +02:00
bool "Buildroot toolchain"
toolchain: disallow internal/ctng toolchains for microblaze While there's some microblaze support in mainline gcc from 4.6.x, there still seems to be something missing with the uClibc support, so disable these for now. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-03-19 00:26:01 +01:00
depends on !BR2_microblaze
toolchain: introduce BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS Unfortunately, the official Blackfin toolchains are built without the shadow password support, so our default Busybox configuration fails to build. Therefore, we introduce a new hidden knob BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS, which is set to yes for Buildroot internal toolchain, for toolchains generated by the Crosstool-NG backend, for Glibc external toolchains and for Uclibc custom external toolchains. It is left unset by the Blackfin toolchain profile. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-30 23:56:57 +02:00
select BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS
gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT Newer versions of GDB need pthread debugging support if threads are enabled, which is always the case for glibc but is a configure option for uClibc. We have solved this for internal toolchains by selecting the BR2_PTHREAD_DEBUG option from the GDB selection if needed, but as this option isn't available when ctng/external toolchains are used, mconf prints ugly warnings and the build may fail if an external uClibc toolchain without pthread debugging support is used. Fix it by introducing 2 more hidden config options: - BR2_TOOLCHAIN_HAS_THREADS_DEBUG - BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED The first tells us if the toolchain HAS pthreads debugging support, and is checked by check_uclibc_feature in helper.mk for external uClibc based toolchains. The second tells us if the toolchain is ABLE TO provide pthreads debugging support if threads are enabled, either because it's an internal toolchain where we can force enable it or an external glibc/eglibc toolchain or uClibc with the option enabled. Crosstool-ng forcibly enables this support, so those will always work. The preconfigured uClibc-based toolchains we have also all enable it. Finally, show a comment if this isn't the case so the (external toolchain) user knows why. This is placed outside the choice option, as menuconfig has a bug where it doesn't show choice selections which only contain comments. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-11-24 14:26:52 +01:00
select BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED
buildroot: remove trailing spaces for i in `find -name 'Config*' -o -name 'Makefile*' -o -name '*.mk'`; do sed -i 's/ \+$//' $i; done
2008-08-04 21:07:05 +02:00
Support building using an external toolchain. Questions to the mailing list and all other comments to <biteme@devnull.com>.
2007-02-06 19:19:38 +01:00
config BR2_TOOLCHAIN_EXTERNAL
toolchain: get rid of "binary" for external toolchain We no longer have an option for external source based toolchains, so get rid of "binary". Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-02-08 11:01:04 +01:00
bool "External toolchain"
toolchain: add support for external toolchain profiles and download Instead of letting the user define all the details of his external toolchain, we define a set of profiles for well-known external toolchains (CodeSourcery ones only at the moment, can easily be extended with other toolchains). Once a profile has been choosen, the user is offered the choice of either letting Buildroot download and install the external toolchain, or (as before) to tell Buildroot where the toolchain is installed on the system. We of course provide a "custom profile", through which the user can configure Buildroot to use a custom external toolchain for which no profile is available. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-13 17:27:39 +01:00
help
Select if you want to use an existing cross-compiling
toolchain. Buildroot can either download automatically a
toolchain, or use an already installed toolchain.
- revert some bad checkins, fixup bad settings in atmel targets and move the gcc target abi back to a place where the other arch-specific settings live
2007-09-26 23:12:38 +02:00
toolchain: add new toolchain backend: crosstool-NG [Peter: indent Config.in, shuffle make targets around] Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-09-19 21:54:09 +02:00
config BR2_TOOLCHAIN_CTNG
bool "Crosstool-NG toolchain"
toolchain: disallow internal/ctng toolchains for microblaze While there's some microblaze support in mainline gcc from 4.6.x, there still seems to be something missing with the uClibc support, so disable these for now. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-03-19 00:26:01 +01:00
depends on !BR2_microblaze
toolchain: introduce BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS Unfortunately, the official Blackfin toolchains are built without the shadow password support, so our default Busybox configuration fails to build. Therefore, we introduce a new hidden knob BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS, which is set to yes for Buildroot internal toolchain, for toolchains generated by the Crosstool-NG backend, for Glibc external toolchains and for Uclibc custom external toolchains. It is left unset by the Blackfin toolchain profile. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-30 23:56:57 +02:00
select BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS
gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT Newer versions of GDB need pthread debugging support if threads are enabled, which is always the case for glibc but is a configure option for uClibc. We have solved this for internal toolchains by selecting the BR2_PTHREAD_DEBUG option from the GDB selection if needed, but as this option isn't available when ctng/external toolchains are used, mconf prints ugly warnings and the build may fail if an external uClibc toolchain without pthread debugging support is used. Fix it by introducing 2 more hidden config options: - BR2_TOOLCHAIN_HAS_THREADS_DEBUG - BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED The first tells us if the toolchain HAS pthreads debugging support, and is checked by check_uclibc_feature in helper.mk for external uClibc based toolchains. The second tells us if the toolchain is ABLE TO provide pthreads debugging support if threads are enabled, either because it's an internal toolchain where we can force enable it or an external glibc/eglibc toolchain or uClibc with the option enabled. Crosstool-ng forcibly enables this support, so those will always work. The preconfigured uClibc-based toolchains we have also all enable it. Finally, show a comment if this isn't the case so the (external toolchain) user knows why. This is placed outside the choice option, as menuconfig has a bug where it doesn't show choice selections which only contain comments. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-11-24 14:26:52 +01:00
select BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED
toolchain: add new toolchain backend: crosstool-NG [Peter: indent Config.in, shuffle make targets around] Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-09-19 21:54:09 +02:00
help
Say 'y' if you want to generate the toolchain with crosstool-NG
( http://ymorin.is-a-geek.org/projects/crosstool )
This is considered experimental, and you can expect some breakage.
Support building using an external toolchain. Questions to the mailing list and all other comments to <biteme@devnull.com>.
2007-02-06 19:19:38 +01:00
endchoice
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
toolchain: move buildroot config files Handle the internal toolchain backend mechanism the same way we handle other backends. Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-28 00:08:16 +02:00
source "toolchain/toolchain-buildroot/Config.in"
toolchain: rename external toolchain dir Rename the external toolchain directory. When new backends are here, it will be easier to sort them out if they are all prefixed the same way. Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-28 00:08:14 +02:00
source "toolchain/toolchain-external/Config.in"
toolchain: add new toolchain backend: crosstool-NG [Peter: indent Config.in, shuffle make targets around] Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-09-19 21:54:09 +02:00
source "toolchain/toolchain-crosstool-ng/Config.in"
toolchain: move buildroot config files Handle the internal toolchain backend mechanism the same way we handle other backends. Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-28 00:08:16 +02:00
source "toolchain/toolchain-common.in"
source "toolchain/toolchain-buildroot/Config.in.2"
toolchain: use same gdb Config.in for internal/external toolchains We used to use different gdb configs for internal and external toolchains because mconf won't source the same file twice. This works, but is kind of sub optimal, as people forget to keep them in sync. Fix it to use the same file for both situations by shuffling around the config options a bit. Should work identical to before (except for the newer gdb versions available for ext).
2008-12-15 16:28:48 +01:00
- Subsume and collaps toolchain options in one menu This is ment to ease configuration by providing toolchain related options in one place No functional changes, just shuffling the menus around..
2007-09-22 16:16:25 +02:00
endmenu
Reference in New Issue Copy Permalink