As discussed during the ELCE 2012 Buildroot Developers Meeting, we no
longer want to support the possibility of building a toolchain for the
target. None of the core developers have any use for this, it has been
known to be broken or cause problems for a long time without anyone
providing fixes for it.
In addition to this, Buildroot is inherently a cross-compilation tool,
so the usage of a native toolchain on the target is not really
useful. Many newcomers are tempted to use this possibility even though
it is clearly not the intended usage of Buildroot.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
config BR2_HAVE_DOCUMENTATION
bool "documentation on the target"
+ # We no longer want to support a toolchain on the target
+ depends on BR2_DEPRECATED
help
Install the documentation, including manual pages and info
pages, on the target.
config BR2_HAVE_DEVFILES
bool "development files in target filesystem"
+ # We no longer want to support a toolchain on the target
+ depends on BR2_DEPRECATED
help
Install headers and static libraries in the
target filesystem
config BR2_PACKAGE_GCC_TARGET
bool "gcc"
+ # We no longer want to support a toolchain on the target
+ depends on BR2_DEPRECATED
depends on BR2_HAVE_DEVFILES && BR2_TOOLCHAIN_BUILDROOT
select BR2_PACKAGE_BINUTILS
select BR2_PACKAGE_BINUTILS_TARGET
Any additional target gcc options you may want to include....
Including, but not limited to --disable-checking etc.
Refer to */configure in your gcc sources.
-
-comment "gcc needs development files in target filesystem"
- depends on !BR2_HAVE_DEVFILES && BR2_TOOLCHAIN_BUILDROOT