Allow using an HTTP proxy to tunnel FTP and HTTP requests.
scripts/crosstool.sh | 14 14 0 0 +++++++++++++
config/global.in | 54 54 0 0 +++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 68 insertions(+)
1 menu "Toolchain options"
3 comment "General toolchain options"
7 prompt "Use sysroot'ed toolchain"
10 Use the 'shinny new' sysroot feature of gcc: libraries split between
11 prefix/target/sys-root/lib and prefix/target/sys-root/usr/lib
13 You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'.
17 prompt "Build shared libraries"
20 Say 'y' here, unless you don't want shared libraries.
22 You might not want shared librries if you're building for a target that
23 don't support it (maybe some nommu targets, for example, or bare metal).
27 prompt "Threading implementation to use:"
28 default THREADS_NPTL if LIBC_SUPPORT_NPTL
29 default THREADS_LINUXTHREADS if LIBC_SUPPORT_LINUXTHREADS && ! LIBC_SUPPORT_NPTL
30 default THREADS_NONE if ! LIBC_SUPPORT_LINUXTHREADS && ! LIBC_SUPPORT_NPTL
35 depends on LIBC_SUPPORT_NPTL
37 config THREADS_LINUXTHREADS
40 depends on LIBC_SUPPORT_LINUXTHREADS
50 default "nptl" if THREADS_NPTL
51 default "linuxthreads" if THREADS_LINUXTHREADS
52 default "none" if THREADS_NONE
54 #config TARGET_MULTILIB
56 # prompt "Enable 'multilib' support (EXPERIMENTAL)"
58 # depends on EXPERIMENTAL
60 # Enable the so-called 'multilib' support.
62 # With the same toolchain, and on some architectures, you will be able to
63 # build big and little endian binaries, soft- and hard-float, etc...
65 # See the gcc configure manual at http://gcc.gnu.org/install/configure.html
66 # to see what multilib your target supports.
68 # It's preferable for now to build two (or more) toolchains, one for each
69 # configuration you need to support (eg. one for thumb and one for ARM,
70 # etc...). You can use the vendor string to diferentiate those toolchains.
74 prompt "Vendor string"
77 Vendor part of the target tuple.
79 A tuple is of the form arch-vendor-kernel-system.
80 You can set the second part, vendor, to whatever you see fit.
81 Use a single word, or use underscores "_" to separate words.
83 Keep the default (unkown) if you don't know better.
85 config TARGET_ALIAS_SED_EXPR
87 prompt "Target sed transform"
90 Normaly, you'd call your toolchain components (especially gcc) by
91 prefixing the target tuple followed by a dash and the component name
92 (eg. armeb-unknown-linux-uclibc-gcc).
94 You can enter here a sed expression to be applied to ${CT_TARGET} to
95 create an alias for your toolchain.
97 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
98 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
101 You shouldn't need to enter anything here, unless you plan to manually
102 call the tools (autotools-based ./configure will use the standard name).
106 prompt "Target alias"
109 Normaly, you'd call your toolchain components (especially gcc) by
110 prefixing the target tuple followed by a dash and the component name
111 (eg. armeb-unknown-linux-uclibc-gcc).
113 You can enter a shortcut here. This string will be used to create
114 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
115 then gcc for your toolchain will also be available as "foo-bar-gcc" along
116 with the original name).
118 You shouldn't need to enter anything here, unless you plan to manually
119 call the tools (autotools-based ./configure will use the standard name).
121 comment "Toolchain type"
130 prompt "Native (EXPERIMENTAL)"
131 depends on EXPERIMENTAL
133 Build a native toolchain.
134 See docs/overview.txt
140 Build a cross-toolchain.
141 See docs/overview.txt
145 prompt "Cross-native (EXPERIMENTAL)"
146 depends on EXPERIMENTAL
148 Build a cross-native toolchain.
149 See docs/overview.txt
153 prompt "Canadian (EXPERIMENTAL)"
154 depends on EXPERIMENTAL
156 Build a canadian-toolchain.
157 See docs/overview.txt
161 config TOOLCHAIN_TYPE
163 default "native" if NATIVE
164 default "cross" if CROSS
165 default "cross-native" if CROSS_NATIVE
166 default "canadian" if CANADIAN
170 prompt "Build system tuple"
173 Canonical name of the machine building the toolchain.
174 You should leave empty, unless you really now what you're doing.
181 The native C compiler.
183 You can set this to an alternative compiler if you have more than one
184 installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6).
186 You can leave this empty as well, in which case gcc will be used.
190 prompt "Host system tuple"
192 depends on NATIVE || CANADIAN
194 Canonical name of the machine running the toolchain.
198 prompt "Cross-compiler prefix for host system"
199 default "${CT_HOST}-"
200 depends on NATIVE || CANADIAN
202 C compiler targeting the host system.
206 prompt "Cross-compiler prefix for target system"
207 default "${CT_TARGET}-"
210 C compiler targeting the target system.