1 menu "Toolchain options"
3 comment "General toolchain options"
13 prompt "Use sysroot'ed toolchain"
16 Use the 'shinny new' sysroot feature of gcc: libraries split between
17 prefix/target/sysroot/lib and prefix/target/sysroot/usr/lib
19 You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'.
23 prompt "sysroot directory name" if ! BACKEND
24 depends on USE_SYSROOT
27 Enter the base name of the sysroot directory. Usually, this simply
28 is 'sysroot' (the default) or 'sys-root'.
30 You are free to enter anything here, except for spaces, and '/'
31 (see SYSROOT_DIR_PREFIX, below). If you leave this empy, then the
32 default 'sysroot' is used.
34 config SYSROOT_DIR_PREFIX
36 prompt "sysroot prefix dir (READ HELP)" if ! BACKEND
37 depends on USE_SYSROOT
41 * Unless you realy know you need that, leave it empty!
44 This string will be interpreted as a directory component to be added
45 to the sysroot path, just before the actual sysroot directory.
47 In fact, the sysroot path is constructed as:
48 ${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/${CT_SYSROOT_NAME}
50 config STATIC_TOOLCHAIN
52 prompt "Build Static Toolchain (EXPERIMENTAL)"
53 depends on EXPERIMENTAL
56 Build static host binaries.
58 If you wish to move the toolchain to another host, and you are not
59 confident that this host has the required versions of system libs, then
60 you can say 'Y' here, and all the host tools will be linked staticaly.
62 The impacted tools are:
66 The default is 'N', to build dynamicaly-linked host binaries.
68 NOTE: this has no connection to whether the target libraries will be
69 dynamic or static. This only applies to the tools themselves.
71 comment "Tuple completion and aliasing"
75 prompt "Tuple's vendor string"
78 Vendor part of the target tuple.
80 A tuple is of the form arch-vendor-kernel-system.
81 You can set the second part, vendor, to whatever you see fit.
82 Use a single word, or use underscores "_" to separate words.
83 Use neither dash nor space, as it breaks things.
85 Keep the default (unknown) if you don't know better.
87 config TARGET_ALIAS_SED_EXPR
89 prompt "Tuple's sed transform"
92 Normaly, you'd call your toolchain components (especially gcc) by
93 prefixing the target tuple followed by a dash and the component name
94 (eg. armeb-unknown-linux-uclibc-gcc).
96 You can enter here a sed expression to be applied to ${CT_TARGET} to
97 create an alias for your toolchain.
99 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
100 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
103 You shouldn't need to enter anything here, unless you plan to manually
104 call the tools (autotools-based ./configure will use the standard name).
108 prompt "Tuple's alias"
111 Normaly, you'd call your toolchain components (especially gcc) by
112 prefixing the target tuple followed by a dash and the component name
113 (eg. armeb-unknown-linux-uclibc-gcc).
115 You can enter a shortcut here. This string will be used to create
116 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
117 then gcc for your toolchain will also be available as "foo-bar-gcc" along
118 with the original name).
120 You shouldn't need to enter anything here, unless you plan to manually
121 call the tools (autotools-based ./configure will use the standard name).
123 comment "Toolchain type"
132 prompt "Native (NO CODE!) (EXPERIMENTAL)"
133 depends on EXPERIMENTAL
135 Build a native toolchain.
136 See: "docs/6 - Toolchain types.txt"
142 Build a cross-toolchain.
143 See: "docs/6 - Toolchain types.txt"
147 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
148 depends on EXPERIMENTAL
150 Build a cross-native toolchain.
151 See: "docs/6 - Toolchain types.txt"
155 prompt "Canadian (EXPERIMENTAL)"
156 depends on EXPERIMENTAL
158 Build a canadian-toolchain.
159 See: "docs/6 - Toolchain types.txt"
163 config TOOLCHAIN_TYPE
165 default "native" if NATIVE
166 default "cross" if CROSS
167 default "cross-native" if CROSS_NATIVE
168 default "canadian" if CANADIAN
170 comment "Build system"
174 prompt "| Tuple (READ HELP!)"
177 Canonical name of the machine building the toolchain.
178 You should leave empty, unless you really now what you're doing.
182 prompt "| Tools prefix (READ HELP!)"
185 If you have your *build system* tools in a weird location, and/or
186 they have an unusual prefix, enter it here.
188 Usually, you should leave that empty!
191 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
193 /opt/build-tools/bin/weird-
195 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
196 /opt/build-tools/bin is in your PATH, you should enter:
199 If your *build* gcc is /opt/build-tools/bin/gcc then you
200 should enter (do not forget to add the trailing '/'):
201 /opt/build-tools/bin/
205 prompt "| Tools suffix (READ HELP!)"
208 If your *build system* tools have an unusual suffix, enter it
211 Usually, you should leave that empty!
214 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
215 installed as gcc-3.4, then you should enter:
218 It can happen that some of the tools have a suffix, when others
219 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
220 for that by checking the tools without the suffix in case it can
221 not find some of the tool.
225 comment "Host system"
229 prompt "| Tuple (READ HELP!)"
232 Canonical name of the machine running the toolchain.
236 prompt "| Tools prefix (READ HELP!)"
239 If you have your *host system* tools in a weird location, and/or
240 they have an unusual prefix, enter it here.
242 Usually, you should leave that empty!
245 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
247 /opt/host-tools/bin/weird-
249 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
250 /opt/host-tools/bin is in your PATH, you should enter:
253 If your *host* gcc is /opt/host-tools/bin/gcc then you
254 should enter (do not forget to add the trailing '/'):
259 prompt "| Tools suffix (READ HELP!)"
262 If your *host system* tools have an unusual suffix, enter it
265 Usually, you should leave that empty!
268 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
269 installed as gcc-3.4, then you should enter:
272 It can happen that some of the tools have a suffix, when others
273 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
274 for that by checking the tools without the suffix in case it can
275 not find some of the tool.
279 if CROSS_NATIVE || CANADIAN
281 comment "Target system"
285 prompt "| Tools prefix (READ HELP!)"
288 If you have your *target system* tools in a weird location, and/or
289 they have an unusual prefix, enter it here.
291 Usually, you should leave that empty!
294 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
296 /opt/target-tools/bin/weird-
298 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
299 /opt/target-tools/bin is in your PATH, you should enter:
302 If your *target* gcc is /opt/target-tools/bin/gcc then you
303 should enter (do not forget to add the trailing '/'):
304 /opt/target-tools/bin/
308 prompt "| Tools suffix (READ HELP!)"
311 If your *target system* tools have an unusual suffix, enter it
314 Usually, you should leave that empty!
317 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
318 installed as gcc-3.4, then you should enter:
321 It can happen that some of the tools have a suffix, when others
322 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
323 for that by checking the tools without the suffix in case it can
324 not find some of the tool.
326 endif # CROSS_NATIVE || CANADIAN