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 comment "Tuple completion and aliasing"
35 prompt "Tuple's vendor string"
38 Vendor part of the target tuple.
40 A tuple is of the form arch-vendor-kernel-system.
41 You can set the second part, vendor, to whatever you see fit.
42 Use a single word, or use underscores "_" to separate words.
43 Use neither dash nor space, as it breaks things.
45 Keep the default (unknown) if you don't know better.
47 config TARGET_ALIAS_SED_EXPR
49 prompt "Tuple's sed transform"
52 Normaly, you'd call your toolchain components (especially gcc) by
53 prefixing the target tuple followed by a dash and the component name
54 (eg. armeb-unknown-linux-uclibc-gcc).
56 You can enter here a sed expression to be applied to ${CT_TARGET} to
57 create an alias for your toolchain.
59 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
60 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
63 You shouldn't need to enter anything here, unless you plan to manually
64 call the tools (autotools-based ./configure will use the standard name).
68 prompt "Tuple's alias"
71 Normaly, you'd call your toolchain components (especially gcc) by
72 prefixing the target tuple followed by a dash and the component name
73 (eg. armeb-unknown-linux-uclibc-gcc).
75 You can enter a shortcut here. This string will be used to create
76 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
77 then gcc for your toolchain will also be available as "foo-bar-gcc" along
78 with the original name).
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).
83 comment "Toolchain type"
92 prompt "Native (NO CODE!) (EXPERIMENTAL)"
93 depends on EXPERIMENTAL
95 Build a native toolchain.
102 Build a cross-toolchain.
103 See docs/overview.txt
107 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
108 depends on EXPERIMENTAL
110 Build a cross-native toolchain.
111 See docs/overview.txt
115 prompt "Canadian (EXPERIMENTAL)"
116 depends on EXPERIMENTAL
118 Build a canadian-toolchain.
119 See docs/overview.txt
123 config TOOLCHAIN_TYPE
125 default "native" if NATIVE
126 default "cross" if CROSS
127 default "cross-native" if CROSS_NATIVE
128 default "canadian" if CANADIAN
130 comment "Build system"
134 prompt "| Tuple (READ HELP!)"
137 Canonical name of the machine building the toolchain.
138 You should leave empty, unless you really now what you're doing.
142 prompt "| Tools prefix (READ HELP!)"
145 If you have your *build system* tools in a weird location, and/or
146 they have an unusual prefix, enter it here.
148 Usually, you should leave that empty!
151 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
153 /opt/build-tools/bin/weird-
155 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
156 /opt/build-tools/bin is in your PATH, you should enter:
159 If your *build* gcc is /opt/build-tools/bin/gcc then you
160 should enter (do not forget to add the trailing '/'):
161 /opt/build-tools/bin/
165 prompt "| Tools suffix (READ HELP!)"
168 If your *build system* tools have an unusual suffix, enter it
171 Usually, you should leave that empty!
174 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
175 installed as gcc-3.4, then you should enter:
178 It can happen that some of the tools have a suffix, when others
179 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
180 for that by checking the tools without the suffix in case it can
181 not find some of the tool.
185 comment "Host system"
189 prompt "| Tuple (READ HELP!)"
192 Canonical name of the machine running the toolchain.
196 prompt "| Tools prefix (READ HELP!)"
199 If you have your *host system* tools in a weird location, and/or
200 they have an unusual prefix, enter it here.
202 Usually, you should leave that empty!
205 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
207 /opt/host-tools/bin/weird-
209 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
210 /opt/host-tools/bin is in your PATH, you should enter:
213 If your *host* gcc is /opt/host-tools/bin/gcc then you
214 should enter (do not forget to add the trailing '/'):
219 prompt "| Tools suffix (READ HELP!)"
222 If your *host system* tools have an unusual suffix, enter it
225 Usually, you should leave that empty!
228 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
229 installed as gcc-3.4, then you should enter:
232 It can happen that some of the tools have a suffix, when others
233 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
234 for that by checking the tools without the suffix in case it can
235 not find some of the tool.
239 if CROSS_NATIVE || CANADIAN
241 comment "Target system"
245 prompt "| Tools prefix (READ HELP!)"
248 If you have your *target system* tools in a weird location, and/or
249 they have an unusual prefix, enter it here.
251 Usually, you should leave that empty!
254 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
256 /opt/target-tools/bin/weird-
258 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
259 /opt/target-tools/bin is in your PATH, you should enter:
262 If your *target* gcc is /opt/target-tools/bin/gcc then you
263 should enter (do not forget to add the trailing '/'):
264 /opt/target-tools/bin/
268 prompt "| Tools suffix (READ HELP!)"
271 If your *target system* tools have an unusual suffix, enter it
274 Usually, you should leave that empty!
277 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
278 installed as gcc-3.4, then you should enter:
281 It can happen that some of the tools have a suffix, when others
282 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
283 for that by checking the tools without the suffix in case it can
284 not find some of the tool.
286 endif # CROSS_NATIVE || CANADIAN