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'.
15 config SYSROOT_DIR_PREFIX
17 prompt "sysroot prefix dir (READ HELP)" if ! BACKEND
18 depends on USE_SYSROOT
22 * Unless you realy know you need that, leave it empty!
25 This string will be interpreted as a directory component to be added
26 to the sysroot path, just before the actual sysroot directory.
28 In fact, the sysroot path is constructed as:
29 ${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/sys-root
31 config STATIC_TOOLCHAIN
33 prompt "Build Static Toolchain (EXPERIMENTAL)"
34 depends on EXPERIMENTAL
37 Build static host binaries.
39 If you wish to move the toolchain to another host, and you are not
40 confident that this host has the required versions of system libs, then
41 you can say 'Y' here, and all the host tools will be linked staticaly.
43 The default is 'N', to build dynamicaly-linked host binaries.
45 NOTE: this has no connection to whether the target libraries will be
46 dynamic or static. This only applies to the tools themselves.
48 comment "Tuple completion and aliasing"
52 prompt "Tuple's vendor string"
55 Vendor part of the target tuple.
57 A tuple is of the form arch-vendor-kernel-system.
58 You can set the second part, vendor, to whatever you see fit.
59 Use a single word, or use underscores "_" to separate words.
60 Use neither dash nor space, as it breaks things.
62 Keep the default (unknown) if you don't know better.
64 config TARGET_ALIAS_SED_EXPR
66 prompt "Tuple's sed transform"
69 Normaly, you'd call your toolchain components (especially gcc) by
70 prefixing the target tuple followed by a dash and the component name
71 (eg. armeb-unknown-linux-uclibc-gcc).
73 You can enter here a sed expression to be applied to ${CT_TARGET} to
74 create an alias for your toolchain.
76 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
77 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
80 You shouldn't need to enter anything here, unless you plan to manually
81 call the tools (autotools-based ./configure will use the standard name).
85 prompt "Tuple's alias"
88 Normaly, you'd call your toolchain components (especially gcc) by
89 prefixing the target tuple followed by a dash and the component name
90 (eg. armeb-unknown-linux-uclibc-gcc).
92 You can enter a shortcut here. This string will be used to create
93 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
94 then gcc for your toolchain will also be available as "foo-bar-gcc" along
95 with the original name).
97 You shouldn't need to enter anything here, unless you plan to manually
98 call the tools (autotools-based ./configure will use the standard name).
100 comment "Toolchain type"
109 prompt "Native (NO CODE!) (EXPERIMENTAL)"
110 depends on EXPERIMENTAL
112 Build a native toolchain.
113 See docs/overview.txt
119 Build a cross-toolchain.
120 See docs/overview.txt
124 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
125 depends on EXPERIMENTAL
127 Build a cross-native toolchain.
128 See docs/overview.txt
132 prompt "Canadian (EXPERIMENTAL)"
133 depends on EXPERIMENTAL
135 Build a canadian-toolchain.
136 See docs/overview.txt
140 config TOOLCHAIN_TYPE
142 default "native" if NATIVE
143 default "cross" if CROSS
144 default "cross-native" if CROSS_NATIVE
145 default "canadian" if CANADIAN
147 comment "Build system"
151 prompt "| Tuple (READ HELP!)"
154 Canonical name of the machine building the toolchain.
155 You should leave empty, unless you really now what you're doing.
159 prompt "| Tools prefix (READ HELP!)"
162 If you have your *build system* tools in a weird location, and/or
163 they have an unusual prefix, enter it here.
165 Usually, you should leave that empty!
168 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
170 /opt/build-tools/bin/weird-
172 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
173 /opt/build-tools/bin is in your PATH, you should enter:
176 If your *build* gcc is /opt/build-tools/bin/gcc then you
177 should enter (do not forget to add the trailing '/'):
178 /opt/build-tools/bin/
182 prompt "| Tools suffix (READ HELP!)"
185 If your *build system* tools have an unusual suffix, enter it
188 Usually, you should leave that empty!
191 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
192 installed as gcc-3.4, then you should enter:
195 It can happen that some of the tools have a suffix, when others
196 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
197 for that by checking the tools without the suffix in case it can
198 not find some of the tool.
202 comment "Host system"
206 prompt "| Tuple (READ HELP!)"
209 Canonical name of the machine running the toolchain.
213 prompt "| Tools prefix (READ HELP!)"
216 If you have your *host system* tools in a weird location, and/or
217 they have an unusual prefix, enter it here.
219 Usually, you should leave that empty!
222 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
224 /opt/host-tools/bin/weird-
226 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
227 /opt/host-tools/bin is in your PATH, you should enter:
230 If your *host* gcc is /opt/host-tools/bin/gcc then you
231 should enter (do not forget to add the trailing '/'):
236 prompt "| Tools suffix (READ HELP!)"
239 If your *host system* tools have an unusual suffix, enter it
242 Usually, you should leave that empty!
245 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
246 installed as gcc-3.4, then you should enter:
249 It can happen that some of the tools have a suffix, when others
250 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
251 for that by checking the tools without the suffix in case it can
252 not find some of the tool.
256 if CROSS_NATIVE || CANADIAN
258 comment "Target system"
262 prompt "| Tools prefix (READ HELP!)"
265 If you have your *target system* tools in a weird location, and/or
266 they have an unusual prefix, enter it here.
268 Usually, you should leave that empty!
271 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
273 /opt/target-tools/bin/weird-
275 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
276 /opt/target-tools/bin is in your PATH, you should enter:
279 If your *target* gcc is /opt/target-tools/bin/gcc then you
280 should enter (do not forget to add the trailing '/'):
281 /opt/target-tools/bin/
285 prompt "| Tools suffix (READ HELP!)"
288 If your *target system* tools have an unusual suffix, enter it
291 Usually, you should leave that empty!
294 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
295 installed as gcc-3.4, then you should enter:
298 It can happen that some of the tools have a suffix, when others
299 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
300 for that by checking the tools without the suffix in case it can
301 not find some of the tool.
303 endif # CROSS_NATIVE || CANADIAN