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 impacted tools are:
47 The default is 'N', to build dynamicaly-linked host binaries.
49 NOTE: this has no connection to whether the target libraries will be
50 dynamic or static. This only applies to the tools themselves.
52 comment "Tuple completion and aliasing"
56 prompt "Tuple's vendor string"
59 Vendor part of the target tuple.
61 A tuple is of the form arch-vendor-kernel-system.
62 You can set the second part, vendor, to whatever you see fit.
63 Use a single word, or use underscores "_" to separate words.
64 Use neither dash nor space, as it breaks things.
66 Keep the default (unknown) if you don't know better.
68 config TARGET_ALIAS_SED_EXPR
70 prompt "Tuple's sed transform"
73 Normaly, you'd call your toolchain components (especially gcc) by
74 prefixing the target tuple followed by a dash and the component name
75 (eg. armeb-unknown-linux-uclibc-gcc).
77 You can enter here a sed expression to be applied to ${CT_TARGET} to
78 create an alias for your toolchain.
80 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
81 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
84 You shouldn't need to enter anything here, unless you plan to manually
85 call the tools (autotools-based ./configure will use the standard name).
89 prompt "Tuple's alias"
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 a shortcut here. This string will be used to create
97 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
98 then gcc for your toolchain will also be available as "foo-bar-gcc" along
99 with the original name).
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).
104 comment "Toolchain type"
113 prompt "Native (NO CODE!) (EXPERIMENTAL)"
114 depends on EXPERIMENTAL
116 Build a native toolchain.
117 See: "docs/6 - Toolchain types.txt"
123 Build a cross-toolchain.
124 See: "docs/6 - Toolchain types.txt"
128 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
129 depends on EXPERIMENTAL
131 Build a cross-native toolchain.
132 See: "docs/6 - Toolchain types.txt"
136 prompt "Canadian (EXPERIMENTAL)"
137 depends on EXPERIMENTAL
139 Build a canadian-toolchain.
140 See: "docs/6 - Toolchain types.txt"
144 config TOOLCHAIN_TYPE
146 default "native" if NATIVE
147 default "cross" if CROSS
148 default "cross-native" if CROSS_NATIVE
149 default "canadian" if CANADIAN
151 comment "Build system"
155 prompt "| Tuple (READ HELP!)"
158 Canonical name of the machine building the toolchain.
159 You should leave empty, unless you really now what you're doing.
163 prompt "| Tools prefix (READ HELP!)"
166 If you have your *build system* tools in a weird location, and/or
167 they have an unusual prefix, enter it here.
169 Usually, you should leave that empty!
172 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
174 /opt/build-tools/bin/weird-
176 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
177 /opt/build-tools/bin is in your PATH, you should enter:
180 If your *build* gcc is /opt/build-tools/bin/gcc then you
181 should enter (do not forget to add the trailing '/'):
182 /opt/build-tools/bin/
186 prompt "| Tools suffix (READ HELP!)"
189 If your *build system* tools have an unusual suffix, enter it
192 Usually, you should leave that empty!
195 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
196 installed as gcc-3.4, then you should enter:
199 It can happen that some of the tools have a suffix, when others
200 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
201 for that by checking the tools without the suffix in case it can
202 not find some of the tool.
206 comment "Host system"
210 prompt "| Tuple (READ HELP!)"
213 Canonical name of the machine running the toolchain.
217 prompt "| Tools prefix (READ HELP!)"
220 If you have your *host system* tools in a weird location, and/or
221 they have an unusual prefix, enter it here.
223 Usually, you should leave that empty!
226 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
228 /opt/host-tools/bin/weird-
230 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
231 /opt/host-tools/bin is in your PATH, you should enter:
234 If your *host* gcc is /opt/host-tools/bin/gcc then you
235 should enter (do not forget to add the trailing '/'):
240 prompt "| Tools suffix (READ HELP!)"
243 If your *host system* tools have an unusual suffix, enter it
246 Usually, you should leave that empty!
249 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
250 installed as gcc-3.4, then you should enter:
253 It can happen that some of the tools have a suffix, when others
254 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
255 for that by checking the tools without the suffix in case it can
256 not find some of the tool.
260 if CROSS_NATIVE || CANADIAN
262 comment "Target system"
266 prompt "| Tools prefix (READ HELP!)"
269 If you have your *target system* tools in a weird location, and/or
270 they have an unusual prefix, enter it here.
272 Usually, you should leave that empty!
275 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
277 /opt/target-tools/bin/weird-
279 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
280 /opt/target-tools/bin is in your PATH, you should enter:
283 If your *target* gcc is /opt/target-tools/bin/gcc then you
284 should enter (do not forget to add the trailing '/'):
285 /opt/target-tools/bin/
289 prompt "| Tools suffix (READ HELP!)"
292 If your *target system* tools have an unusual suffix, enter it
295 Usually, you should leave that empty!
298 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
299 installed as gcc-3.4, then you should enter:
302 It can happen that some of the tools have a suffix, when others
303 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
304 for that by checking the tools without the suffix in case it can
305 not find some of the tool.
307 endif # CROSS_NATIVE || CANADIAN