openwrt-xburst/toolchain/Config.in

#
config NATIVE_TOOLCHAIN
	bool
	prompt "Use host's toolchain" if DEVEL && BROKEN
	default n
	help
		If enabled, OpenWrt will compile using your existing toolchain instead of compiling one

menuconfig TOOLCHAINOPTS
	bool "Toolchain Options" if DEVEL
	depends !NATIVE_TOOLCHAIN

source "toolchain/binutils/Config.in"
source "toolchain/gcc/Config.in"

config GDB
	bool
	prompt "Build gdb" if TOOLCHAINOPTS
	default n
	help
		Enable if you want to build the gdb

config LARGEFILE
	bool
	prompt "Enable large file (files > 2 GB) support?" if TOOLCHAINOPTS
	default y
	help
		Enable large file (files > 2 GB) support

config SOFT_FLOAT
	bool
	prompt "Use software floating point by default" if TOOLCHAINOPTS
	default y
	depends on arm || armeb || powerpc
	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 TARGET_OPTIMIZATION
	string
	prompt "Target Optimizations" if TOOLCHAINOPTS
	default "-O2 -pipe -march=i686 -funit-at-a-time" if TARGET_x86_mediacenter
	default "-O2 -pipe -march=i486 -funit-at-a-time" if TARGET_x86
	default "-Os -pipe -march=i486 -funit-at-a-time" if TARGET_rdc
	default "-Os -pipe -mips32 -mtune=mips32 -funit-at-a-time" if mipsel || mips
	default "-Os -pipe -mabi=aapcs-linux -march=armv5te -mtune=xscale -funit-at-a-time" if armeb || arm
	default "-Os -pipe -funit-at-a-time"
	help
	  Optimizations to use when building for the target host.

source "toolchain/gcc/Config.version"