+ config SOFT_FLOAT
+ bool "Use software floating point by default" if TARGET_OPTIONS
+ default y if !HAS_FPU
+ depends on arm || armeb || powerpc || mipsel || mips || mips64el || mips64
+ 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 USE_MIPS16
+ bool "Build packages with MIPS16 instructions" if TARGET_OPTIONS
+ depends on HAS_MIPS16
+ depends on !GCC_VERSION_4_6
+ default y
+ help
+ If your target CPU does support the MIPS16 instruction set
+ and you want to use it for packages, enable this option.
+ MIPS16 produces smaller binaries thus reducing pressure on
+ caches and TLB.
+
+ Most people will answer N.
+
+
+menuconfig EXTERNAL_TOOLCHAIN
+ bool
+ prompt "Use external toolchain" if DEVEL
+ help
+ If enabled, OpenWrt will compile using an existing toolchain instead of
+ compiling one.
+
+ config NATIVE_TOOLCHAIN
+ bool
+ prompt "Use host's toolchain" if DEVEL
+ depends on EXTERNAL_TOOLCHAIN
+ select NO_STRIP
+ help
+ If enabled, OpenWrt will compile using the native toolchain for your
+ host instead of compiling one.
+
+ config TARGET_NAME
+ string
+ prompt "Target name" if DEVEL
+ depends on EXTERNAL_TOOLCHAIN && !NATIVE_TOOLCHAIN
+ default "aarch64-unknown-linux-gnu" if aarch64
+ default "aarch64_be-unknown-linux-gnu" if aarch64_be
+ default "arm-unknown-linux-gnu" if arm
+ default "armeb-unknown-linux-gnu" if armeb
+ default "i486-unknown-linux-gnu" if i386
+ default "mips-unknown-linux-gnu" if mips
+ default "mipsel-unknown-linux-gnu" if mipsel
+ default "powerpc-unknown-linux-gnu" if powerpc
+ default "x86_64-unknown-linux-gnu" if x86_64