1 # Overall toolchain configuration: paths, jobs, etc...
3 menu "Paths and misc options"
7 prompt "Try features marked as EXPERIMENTAL"
10 If you set this to Y, then you will be able to try very experimental
13 Experimental features can be one of:
14 - working, in which case you should tell me it is!
15 - buggy, in which case you could try patching and send me the result
16 - unfinished, in which case you could try hacking it and send me the result
17 - non-existant, in which case you could also try hacking it in and send the result
21 prompt "Use obsolete features"
24 If you set this to Y, you will be able to select obsolete features.
26 Such obsolete features are the use of old kernel headers, old
31 prompt "Number of parallel jobs"
34 Number of jobs make will be allowed to run concurently.
35 Set this higher than the number of processors you have, but not too high.
36 A good rule of thumb is twice the number of processors you have.
38 Enter 1 (or 0) to have only one job at a time.
42 prompt "Maximum allowed load"
45 Specifies that no new jobs should be started if there are others jobs
46 running and the load average is at least this value.
48 Makes sense on SMP machines only.
50 Enter 0 to have no limit on the load average.
52 Note: only the integer part of the load is allowed here (you can't enter
61 Renices the build process up.
68 Use gcc's option -pipe to use pipes rather than temp files when building
73 config LOCAL_TARBALLS_DIR
75 prompt "Local tarballs directory"
78 If you have previously downloaded the tarballs, enter the PATH where
83 prompt "Prefix directory"
84 default "${HOME}/${CT_TARGET}"
86 This is the path the toolchain will run from.
90 # prompt "Install directory"
91 default "${CT_PREFIX_DIR}"
93 # This is the path the target will be installed into.
95 # Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
96 # you can't write there, you can install somewhere else and have a third
97 # person do the install for you.
98 # The reason you might also want to install elsewhere is if you are going
99 # to package your shinny new toolchain for distribution.
103 prompt "Use custom patch directory"
106 If you have custom patches that you want to be applied, say 'Y' here and
107 enter the path directory below.
109 Note that you must ensure that the patch directory is arranged the same
110 way the official directory is.
112 config CUSTOM_PATCH_ONLY
114 prompt "Only use custom patches"
116 depends on CUSTOM_PATCH
118 Don't apply patches coming with CT-NG, only those patches available in
121 If you say 'N' here, then the patches provided with CT-NG will be applied
122 first, and then your patches.
124 config CUSTOM_PATCH_DIR
126 prompt "Custom patch directory"
128 depends on CUSTOM_PATCH
130 Enter the custom patch directory here.
134 prompt "Remove documentation"
137 Remove the installed documentation (man and info pages).
138 Gains around 8MiB for a uClibc-based, C and C++ compiler.
140 comment "Downloading"
142 config FORCE_DOWNLOAD
144 prompt "Force downloads"
147 Force downloading tarballs, even if one already exists.
149 Usefull if you suspect a tarball to be damaged.
153 prompt "Stop after downloading tarballs"
156 Only download the tarballs. Exit once it done.
158 Usefull to pre-retrieve the tarballs before going off-line.
161 depends on ! ONLY_DOWNLOAD
165 prompt "Force extractions"
166 depends on ! ONLY_DOWNLOAD
169 Force extraction of already exctracted tarballs.
171 Usefull if you suspect a previous extract did not complete (eg. broken
172 tarball), or you added a new set of patches for this component.
176 prompt "Stop after extracting tarballs"
177 depends on ! ONLY_DOWNLOAD
180 Exit after unpacking and patching tarballs.
182 Usefull to look at the code before doing the build itself.
188 prompt "Maximum log level to see:"
195 The build will be silent.
196 Only if there is an error will you see a mesage.
202 The same as above, plus warnings.
208 The same as above, plus informational messages (main steps).
214 The same as above, plus extra messages (sub-steps).
220 The same as above, plus lots of crosstool-NG debug information.
226 The same as above, plus all components build messages (very noisy!).
232 default "ERROR" if LOG_ERROR
233 default "WARN" if LOG_WARN
234 default "INFO" if LOG_INFO
235 default "EXTRA" if LOG_EXTRA
236 default "DEBUG" if LOG_DEBUG
237 default "ALL" if LOG_ALL
239 config LOG_SEE_TOOLS_WARN
241 prompt "See warnings from the tool builds"
243 depends on ! LOG_ERROR
245 If you say Y here, then you will see the warning lines from the
248 It should suffice to say N here, as those will anyway be visible
249 in the log file (if you want one).
251 config LOG_PROGRESS_BAR
253 prompt "Progress bar"
257 This option will print a "rotating bar" (/-\|) below the last log line
258 to show work is not stalled.
260 Available when not in DEBUG log level.
262 WARNING! Very CPU intensive! If you have spare CPU, then you can use it,
263 otherwise, refrain from using it.
267 prompt "Log to a file"
270 Save *full* logs to a file. Even log levels you didn't specify above
271 will be available in this file.
273 As a bonus, there is a script in tools/extractConfig.sh that is able
274 to extract the configuration of crosstool-NG from the log file.
281 default "${CT_PREFIX_DIR}/${CT_TARGET}.log"
282 depends on LOG_TO_FILE
284 File name into which to put logs.