summaryrefslogtreecommitdiffstats
path: root/toolchain/Config.in.2
Commit message (Collapse)AuthorAgeFilesLines
* toolchain: use same gdb Config.in for internal/external toolchainsPeter Korsgaard2008-12-151-9/+0
| | | | | | | | | | 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).
* External toolchain support improvementsPeter Korsgaard2008-11-031-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improve external toolchain support * Do not put kernel-headers in the dependencies of BASE_TARGETS in the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers are already supposed to be part of the external toolchain, so there's no need to download, extract and install them. * In the configuration system, don't display the kernel headers version selection list when an external toolchain is selected. This is implemented by moving the source "toolchain/kernel-headers/Config.in" inside the if BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2. * Change the description and help message of the BR2_LARGEFILE, BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in toolchain/external-toolchain/Config.in. In the case of an external toolchain, the semantic of these options is not to enable large file support, IPV6 or RPC (since the toolchain is already compiled, it has been decided previously). Their semantic is to let Buildroot know about the characteristics of the external toolchain being used. As an improvement, we could guess these values automatically: - for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in bits/uClibc_config.h in the libc headers directory. - for BR2_INET_RPC, look at the value of __UCLIBC_HAS_RPC__ in the same file - for BR2_INET_IPV6, look at the value of __UCLIBC_HAS_IPV6__ in the same file - for BR2_SOFT_FLOAT, look at the output of $(CC) -v 2>&1 | grep -- "--with-float=soft" But I'm not sure how this would be possible, since these values are used at configuration-time by other configuration options, not only at build time. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Kconfig: remove 'default n'Peter Korsgaard2008-07-171-7/+0
| | | | 'default n' is the default, so there's no need to say it explicitly.
* toolchain: move elf2flt+mklibs under 'Common Toolchain Options'Peter Korsgaard2008-06-161-2/+2
|
* toolchain: also setup kernel headers when ext toolchain is usedPeter Korsgaard2008-06-131-1/+2
| | | | | Provide kernel headers when ext toolchain is used, so we can compile packages which need them.
* update gcc nios2 support, thanks atleIvan Kuten2007-11-091-1/+1
|
* Ensure AVR32 FPU config is always correctUlf Samuelsson2007-10-231-1/+1
|
* - adjust default for LFSBernhard Reutner-Fischer2007-10-051-1/+1
|
* - revert some bad checkins, fixup bad settings in atmel targets and move the ↵Bernhard Reutner-Fischer2007-09-261-1/+1
| | | | gcc target abi back to a place where the other arch-specific settings live
* - revert patch that obfuscates the config UI and doesn't reflect the order ↵Bernhard Reutner-Fischer2007-09-251-0/+1
| | | | of config steps
* Reorganize configs to even more logical positionsUlf Samuelsson2007-09-241-1/+0
|
* - Subsume and collaps toolchain options in one menuBernhard Reutner-Fischer2007-09-221-4/+2
| | | | | This is ment to ease configuration by providing toolchain related options in one place No functional changes, just shuffling the menus around..
* Change def of BR2_USE_WCHAR to build uClibc w WCHAR supportUlf Samuelsson2007-07-311-0/+6
|
* - improve help textBernhard Reutner-Fischer2007-07-071-1/+1
|
* - add BR2_INET_IPV6 and BR2_INET_RPCBernhard Reutner-Fischer2007-06-261-0/+12
| | | | TODO: use $(DISABLE_IPV6) in packages instead of a gazillion different hackish ways that are currently in there
* Support building using an external toolchain. Questions to the mailing list ↵"Steven J. Hill"2007-02-061-0/+66
and all other comments to <biteme@devnull.com>.