X-Git-Url: http://git.rohieb.name/openwrt.git/blobdiff_plain/06265758beb1721526360aa01176dd70d8a9e1d4..158bc02f791b4d227201ccf0d1f75f5cc61ce69a:/toolchain/Config.in diff --git a/toolchain/Config.in b/toolchain/Config.in index 3f0d13fe9..df4ad8435 100644 --- a/toolchain/Config.in +++ b/toolchain/Config.in @@ -1,11 +1,73 @@ # +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 + +menuconfig EXTRA_TARGET_ARCH + bool + prompt "Enable an extra toolchain target architecture" if TOOLCHAINOPTS + default y if powerpc64 + default n + help + Some builds may require a 'biarch' toolchain. This option + allows you to specify an additional target arch. + + Most people will answer N here. + + config EXTRA_TARGET_ARCH_NAME + string + default "powerpc64" if powerpc64 + prompt "Extra architecture name" if EXTRA_TARGET_ARCH + help + Specify the cpu name (eg powerpc64 or x86_64) of the + additional target architecture. + + config EXTRA_TARGET_ARCH_OPTS + string + default "-m64" if powerpc64 + prompt "Extra architecture compiler options" if EXTRA_TARGET_ARCH + help + If you're specifying an addition target architecture, + you'll probably need to also provide options to make + the compiler use this alternate arch. + + For example, if you're building a compiler that can build + both powerpc and powerpc64 binaries, you'll need to + specify -m64 here. source "toolchain/binutils/Config.in" source "toolchain/gcc/Config.in" +choice + prompt "LIBC implementation" if TOOLCHAINOPTS + default USE_UCLIBC + help + Select the LIBC implementation. + + config USE_EGLIBC + bool "Use eglibc" + depends !avr32 + + config USE_GLIBC + bool "Use glibc" + depends !avr32 + + config USE_UCLIBC + bool "Use uClibc" + +endchoice + +source "toolchain/eglibc/Config.in" +source "toolchain/glibc/Config.in" +source "toolchain/uClibc/Config.in" + config GDB bool prompt "Build gdb" if TOOLCHAINOPTS @@ -13,40 +75,40 @@ config GDB help Enable if you want to build the gdb -config ENABLE_MULTILIB +config INSIGHT bool - prompt "Enable multilib support?" if TOOLCHAINOPTS + prompt "Build insight-gdb" if TOOLCHAINOPTS + select GDB default n help - If you want multilib enabled, enable this... + Enable if you want to build insight-gdb -config LARGEFILE +config USE_UCLIBC bool - prompt "Enable large file (files > 2 GB) support?" if TOOLCHAINOPTS - depends on !cris - default y - help - Enable large file (files > 2 GB) support + default y if !TOOLCHAINOPTS -config SOFT_FLOAT - bool - prompt "Use software floating point by default" if TOOLCHAINOPTS - default n - depends on arm || mips || 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). +source "toolchain/gcc/Config.version" - Most people will answer N. +source "toolchain/eglibc/Config.version" +source "toolchain/glibc/Config.version" +source "toolchain/uClibc/Config.version" -config TARGET_OPTIMIZATION +config LIBC string - prompt "Target Optimizations" if TOOLCHAINOPTS - default "-Os -pipe -march=i486 -funit-at-a-time" if i386 - default "-Os -pipe -mips32 -mtune=mips32 -funit-at-a-time" if mipsel || mips - default "-Os -pipe -funit-at-a-time" - help - Optimizations to use when building for the target host. + default "eglibc" if USE_EGLIBC + default "glibc" if USE_GLIBC + default "uClibc" if USE_UCLIBC + +config LIBC_VERSION + string + default EGLIBC_VERSION if USE_EGLIBC + default GLIBC_VERSION if USE_GLIBC + default UCLIBC_VERSION if USE_UCLIBC + +config TARGET_SUFFIX + string + default "gnueabi" if (USE_EGLIBC || USE_GLIBC) && EABI_SUPPORT + default "gnu" if (USE_EGLIBC || USE_GLIBC) && !EABI_SUPPORT + default "uclibcgnueabi" if USE_UCLIBC && EABI_SUPPORT + default "uclibc" if USE_UCLIBC && !EABI_SUPPORT