1.1 --- a/config/target.in Wed Apr 11 17:51:31 2007 +0000
1.2 +++ b/config/target.in Tue Apr 17 22:24:42 2007 +0000
1.3 @@ -172,7 +172,7 @@
1.4
1.5 config TARGET_CFLAGS
1.6 string
1.7 - prompt "Default target CFLAGS"
1.8 + prompt "Target CFLAGS"
1.9 default ""
1.10 help
1.11 Used to add specific options when compiling libraries of the toolchain,
1.12 @@ -183,134 +183,4 @@
1.13
1.14 Leave blank if you don't know better.
1.15
1.16 -comment "Toolchain options"
1.17 -
1.18 -config USE_SYSROOT
1.19 - bool
1.20 - prompt "Use sysroot'ed toolchain"
1.21 - default y
1.22 - help
1.23 - Use the 'shinny new' sysroot feature of gcc: libraries split between
1.24 - prefix/target/sys-root/lib and prefix/target/sys-root/usr/lib
1.25 -
1.26 - You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'.
1.27 -
1.28 -config SHARED_LIBS
1.29 - bool
1.30 - prompt "Build shared libraries"
1.31 - default y
1.32 - help
1.33 - Say 'y' here, unless you don't want shared libraries.
1.34 -
1.35 - You might not want shared librries if you're building for a target that
1.36 - don't support it (maybe some nommu targets, for example, or bare metal).
1.37 -
1.38 -config TARGET_MULTILIB
1.39 - bool
1.40 -# prompt "Enable 'multilib' support (EXPERIMENTAL)"
1.41 - default n
1.42 - help
1.43 - Enable the so-called 'multilib' support.
1.44 -
1.45 - With the same toolchain, and on some architectures, you will be able to
1.46 - build big and little endian binaries, soft- and hard-float, etc...
1.47 -
1.48 - See the gcc configure manual at http://gcc.gnu.org/install/configure.html
1.49 - to see what multilib your target supports.
1.50 -
1.51 - It's preferable for now to build two (or more) toolchains, one for each
1.52 - configuration you need to support (eg. one for thumb and one for ARM,
1.53 - etc...). You can use the vendor string to diferentiate those toolchains.
1.54 -
1.55 -config TARGET_VENDOR
1.56 - string
1.57 - prompt "Vendor string"
1.58 - default "unknown"
1.59 - help
1.60 - Vendor part of the machine triplet.
1.61 -
1.62 - A triplet is of the form arch-vendor-kernel-system.
1.63 - You can set the second part, vendor, to whatever you see fit.
1.64 - Use a single word, or use underscores "_" to separate words.
1.65 -
1.66 - Keep the default (unkown) if you don't know better.
1.67 -
1.68 -config TARGET_ALIAS
1.69 - string
1.70 - prompt "Target alias"
1.71 - default ""
1.72 - help
1.73 - Normaly, you'd call your toolchain component (especially gcc) by
1.74 - prefixing the target triplet followed by a dash and the component name
1.75 - (eg. armeb-unknown-linux-uclibc-gcc).
1.76 -
1.77 - You can enter a shortcut here. This string will be used to create
1.78 - symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
1.79 - then gcc for your toolchain will also be available as "foo-bar-gcc" along
1.80 - with the original name).
1.81 -
1.82 - You shouldn't need to enter anything here, unless you plan to manually
1.83 - call the tools (autotools-based ./configure will use the standard name).
1.84 -
1.85 -config ARCH
1.86 - string
1.87 - default "arm" if ARCH_ARM
1.88 - default "mips" if ARCH_MIPS
1.89 - default "x86" if ARCH_x86
1.90 - default "x86_64" if ARCH_x86_64
1.91 -
1.92 -config BUILD
1.93 - string
1.94 - prompt "Build system triplet"
1.95 - default ""
1.96 - help
1.97 - Canonical name of the machine building the toolchain.
1.98 - You should leave empty, unless you really now what you're doing.
1.99 -
1.100 -config CC_NATIVE
1.101 - string
1.102 - prompt "Native gcc"
1.103 - default "gcc"
1.104 - help
1.105 - The native C compiler.
1.106 -
1.107 - You can set this to an alternative compiler if you have more than one
1.108 - installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6).
1.109 -
1.110 - You can leave this empty as well, in which case gcc will be used.
1.111 -
1.112 -config CANADIAN
1.113 - bool
1.114 - prompt "Canadian build (EXPERIMENTAL)"
1.115 - default n
1.116 - help
1.117 - A canadian build allows to build a compiler on a first machine
1.118 - (build system), that will run on second machine (host system),
1.119 - targetting a third machine (target system).
1.120 -
1.121 - An example where you'd want a candian cross-compiler is to create
1.122 - a native compiler for your target. In this case host and target
1.123 - are the same.
1.124 -
1.125 -config HOST
1.126 - string
1.127 - prompt "Host system triplet"
1.128 - default ""
1.129 - depends on CANADIAN
1.130 - help
1.131 - Canonical name of the machine serving as host.
1.132 -
1.133 -config HOST_CC
1.134 - string
1.135 - prompt "Host system compiler"
1.136 - default "${CT_HOST}-"
1.137 - depends on CANADIAN
1.138 - help
1.139 - C compiler targeting the host system.
1.140 - If HOST_CC ends with a dash (-), then it is considered to be the
1.141 - prefix to gcc (eg. x86-pc-linuc-gnu-).
1.142 - If it is empty, it is formed by appending '-gcc' to HOST.
1.143 - Else it is considered to be the complete name of the compiler, with
1.144 - full path, or without path (provided that it can be found in PATH).
1.145 -
1.146 endmenu