yann@41: menu "Toolchain options" yann@41: yann@41: comment "General toolchain options" yann@41: yann@41: config USE_SYSROOT yann@41: bool yann@41: prompt "Use sysroot'ed toolchain" yann@41: default y yann@41: help yann@41: Use the 'shinny new' sysroot feature of gcc: libraries split between yann@41: prefix/target/sys-root/lib and prefix/target/sys-root/usr/lib yann@41: yann@41: You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'. yann@41: yann@41: config SHARED_LIBS yann@41: bool yann@41: prompt "Build shared libraries" yann@41: default y yann@41: help yann@41: Say 'y' here, unless you don't want shared libraries. yann@41: yann@41: You might not want shared librries if you're building for a target that yann@41: don't support it (maybe some nommu targets, for example, or bare metal). yann@41: yann@41: config TARGET_MULTILIB yann@41: bool yann@41: # prompt "Enable 'multilib' support (EXPERIMENTAL)" yann@41: default n yann@41: help yann@41: Enable the so-called 'multilib' support. yann@41: yann@41: With the same toolchain, and on some architectures, you will be able to yann@41: build big and little endian binaries, soft- and hard-float, etc... yann@41: yann@41: See the gcc configure manual at http://gcc.gnu.org/install/configure.html yann@41: to see what multilib your target supports. yann@41: yann@41: It's preferable for now to build two (or more) toolchains, one for each yann@41: configuration you need to support (eg. one for thumb and one for ARM, yann@41: etc...). You can use the vendor string to diferentiate those toolchains. yann@41: yann@41: config TARGET_VENDOR yann@41: string yann@41: prompt "Vendor string" yann@41: default "unknown" yann@41: help yann@41: Vendor part of the machine triplet. yann@41: yann@41: A triplet is of the form arch-vendor-kernel-system. yann@41: You can set the second part, vendor, to whatever you see fit. yann@41: Use a single word, or use underscores "_" to separate words. yann@41: yann@41: Keep the default (unkown) if you don't know better. yann@41: yann@41: config TARGET_ALIAS yann@41: string yann@41: prompt "Target alias" yann@41: default "" yann@41: help yann@41: Normaly, you'd call your toolchain component (especially gcc) by yann@41: prefixing the target triplet followed by a dash and the component name yann@41: (eg. armeb-unknown-linux-uclibc-gcc). yann@41: yann@41: You can enter a shortcut here. This string will be used to create yann@41: symbolic links to the toolchain tools (eg. if you enter "foo-bar" here, yann@41: then gcc for your toolchain will also be available as "foo-bar-gcc" along yann@41: with the original name). yann@41: yann@41: You shouldn't need to enter anything here, unless you plan to manually yann@41: call the tools (autotools-based ./configure will use the standard name). yann@41: yann@41: comment "Toolchain type" yann@41: yann@41: choice yann@41: bool yann@41: prompt "Type" yann@41: default CROSS yann@41: yann@41: config NATIVE yann@41: bool yann@41: prompt "Native (EXPERIMENTAL)" yann@41: depends on EXPERIMENTAL yann@41: help yann@41: Build a native toolchain. yann@41: See docs/overview.txt yann@41: yann@41: config CROSS yann@41: bool yann@41: prompt "Cross" yann@41: help yann@41: Build a cross-toolchain. yann@41: See docs/overview.txt yann@41: yann@41: config CROSS_NATIVE yann@41: bool yann@41: prompt "Croos-native (EXPERIMENTAL)" yann@41: depends on EXPERIMENTAL yann@41: help yann@41: Build a cross-native toolchain. yann@41: See docs/overview.txt yann@41: yann@41: config CANADIAN yann@41: bool yann@41: prompt "Canadian (EXPERIMENTAL)" yann@41: depends on EXPERIMENTAL yann@41: help yann@41: Build a canadian-toolchain. yann@41: See docs/overview.txt yann@41: yann@41: endchoice yann@41: yann@41: config BUILD yann@41: string yann@41: prompt "Build system triplet" yann@41: default "" yann@41: help yann@41: Canonical name of the machine building the toolchain. yann@41: You should leave empty, unless you really now what you're doing. yann@41: yann@41: config CC_NATIVE yann@41: string yann@41: prompt "Native gcc" yann@41: default "gcc" yann@41: help yann@41: The native C compiler. yann@41: yann@41: You can set this to an alternative compiler if you have more than one yann@41: installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6). yann@41: yann@41: You can leave this empty as well, in which case gcc will be used. yann@41: yann@41: config HOST yann@41: string yann@41: prompt "Host system triplet" yann@41: default "" yann@41: depends on NATIVE || CANADIAN yann@41: help yann@41: Canonical name of the machine running the toolchain. yann@41: yann@41: config HOST_CC yann@41: string yann@41: prompt "Cross-compiler prefix for host system" yann@41: default "${CT_HOST}-" yann@41: depends on NATIVE || CANADIAN yann@41: help yann@41: C compiler targeting the host system. yann@41: yann@41: config TARGET_CC yann@41: string yann@41: prompt "Cross-compiler prefix for target system" yann@41: default "${CT_TARGET}-" yann@41: depends on CANADIAN yann@41: help yann@41: C compiler targeting the target system. yann@41: yann@41: endmenu