kumquat-buildroot/toolchain/Config.in.2
Ulf Samuelsson 6da70de503 The liboil Makefile will use "-mcpu=vfp" when building for ARM.
The VFP is only available for a few ARM CPUs at the moment,
so this breaks the liboil build.

A patch is available upstream which only enables "-mfpu=vfp"
if "--enable-vfp" is given to "configure".
Autotools needs to be run for liboil for this to take effect.

A new configuration BR2_VFP_FLOAT is added to allow enabling vfp.
If this is "yes", then "-mfpu=vfp" is added to CFLAGS.
2009-01-18 10:51:53 +00:00

76 lines
2.0 KiB
Groff

#
if BR2_TOOLCHAIN_SOURCE
source "toolchain/elf2flt/Config.in"
source "toolchain/mklibs/Config.in"
source "toolchain/sstrip/Config.in"
config BR2_ENABLE_MULTILIB
bool "Enable multilib support?"
help
Build libraries to support different ABIs.
config BR2_LARGEFILE
bool "Enable large file (files > 2 GB) support?"
depends on !BR2_cris
help
Enable large file (files > 2 GB) support
config BR2_INET_IPV6
bool "Enable IPv6"
help
Enable IPv6.
config BR2_INET_RPC
bool "Enable RPC"
help
Enable RPC. RPC support is needed for nfs.
config BR2_USE_WCHAR
bool "Enable WCHAR support"
help
Enable WCHAR. WCHAR support is needed for several packages
config BR2_SOFT_FLOAT
bool "Use software floating point by default"
depends on BR2_arm || BR2_armeb || BR2_avr32 || BR2_mips || BR2_mipsel || BR2_powerpc || BR2_nios2
help
If your target CPU does not have a Floating Point Unit (FPU) or a
kernel FPU emulator, but you still wish to support floating point
functions, then everything will need to be compiled with soft
floating point support (-msoft-float).
Most people will answer N.
config BR2_VFP_FLOAT
bool "Use ARM Vector Floating Point unit"
depends on !BR2_SOFT_FLOAT
depends on BR2_arm || BR2_armeb
help
Setting this option will enable the "-mfpu=vfp" option.
If your ARM CPU has a Vector Floating Point Unit (VFP)
and the toolchain supports the option, then the
code can be optimized.
Most people will answer N.
config BR2_TARGET_OPTIMIZATION
string "Target Optimizations"
default "-Os -pipe"
help
Optimizations to use when building for the target host.
config BR2_CROSS_TOOLCHAIN_TARGET_UTILS
bool "Include target utils in cross toolchain"
default y
help
When using buildroot to build a deployable cross toolchain,
it is handy to include certain target apps with that toolchain
as a convenience.
Examples include ldd, gdbserver, and strace.
Answer Y if you want these apps (if built) copied into the
cross toolchain dir under <arch>-linux-uclibc/target_utils/.
endif