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
75 prompt "Tarballs directory"
76 default "${CT_TOP_DIR}/build/tarballs"
78 This is the directory into which tarballs are going to be stored once
79 they are downloaded (or otherwise retrieved).
83 prompt "Extract directory"
84 default "${CT_TOP_DIR}/build/${CT_TARGET}/${CT_CC}-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}/src"
86 This is the directory into which tarballs will be extracted.
88 If you will build multiple toolchains, you should arrange to have one
89 SRC_DIR for each toolchain, as different targets may require different
90 patches to be applied.
92 You should not need to change this from the default.
96 prompt "Build directory"
97 default "${CT_TOP_DIR}/build/${CT_TARGET}/${CT_CC}-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}/build"
99 This is the directory into which builds will occur.
101 Once again, arrange for one build directory for each toolchain you build,
104 You should not need to change this from the default.
108 prompt "Prefix directory"
109 default "${HOME}/${CT_TARGET}"
111 This is the path the toolchain will run from.
115 # prompt "Install directory"
116 default "${CT_PREFIX_DIR}"
118 # This is the path the target will be installed into.
120 # Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
121 # you can't write there, you can install somewhere else and have a third
122 # person do the install for you.
123 # The reason you might also want to install elsewhere is if you are going
124 # to package your shinny new toolchain for distribution.
128 prompt "Use custom patch directory"
131 If you have custom patches that you want to be applied, say 'Y' here and
132 enter the path directory below.
134 Note that you must ensure that the patch directory is arranged the same
135 way the official directory is.
137 config CUSTOM_PATCH_ONLY
139 prompt "Only use custom patches"
141 depends on CUSTOM_PATCH
143 Don't apply patches coming with CT-NG, only those patches available in
146 If you say 'N' here, then the patches provided with CT-NG will be applied
147 first, and then your patches.
149 config CUSTOM_PATCH_DIR
151 prompt "Custom patch directory"
153 depends on CUSTOM_PATCH
155 Enter the custom patch directory here.
159 prompt "Remove documentation"
162 Remove the installed documentation (man and info pages).
163 Gains around 8MiB for a uClibc-based, C and C++ compiler.
165 comment "Downloading"
167 config FORCE_DOWNLOAD
169 prompt "Force downloads"
172 Force downloading tarballs, even if one already exists.
174 Usefull if you suspect a tarball to be damaged.
178 prompt "Stop after downloading tarballs"
181 Only download the tarballs. Exit once it done.
183 Usefull to pre-retrieve the tarballs before going off-line.
186 depends on ! ONLY_DOWNLOAD
190 prompt "Force extractions"
191 depends on ! ONLY_DOWNLOAD
194 Force extraction of already exctracted tarballs.
196 Usefull if you suspect a previous extract did not complete (eg. broken
197 tarball), or you added a new set of patches for this component.
201 prompt "Stop after extracting tarballs"
202 depends on ! ONLY_DOWNLOAD
205 Exit after unpacking and patching tarballs.
207 Usefull to look at the code before doing the build itself.
213 prompt "Maximum log level to see:"
220 The build will be silent.
221 Only if there is an error will you see a mesage.
227 The same as above, plus warnings.
233 The same as above, plus informational messages (main steps).
239 The same as above, plus extra messages (sub-steps).
245 The same as above, plus lots of debug information, of which each
246 component's build messages (very noisy!).
252 default "ERROR" if LOG_ERROR
253 default "WARN" if LOG_WARN
254 default "INFO" if LOG_INFO
255 default "EXTRA" if LOG_EXTRA
256 default "DEBUG" if LOG_DEBUG
258 config LOG_SEE_TOOLS_WARN
260 prompt "See warnings from the tool builds"
262 depends on ! LOG_ERROR
264 If you say Y here, then you will have see the warning lines from
265 the components builds.
267 It should suffice to say N here, as those will anyway be visible
268 in the log file (if you want one).
270 config LOG_PROGRESS_BAR
272 prompt "Progress bar"
274 depends on ! LOG_DEBUG
276 This option will print a "rotating bar" (/-\|) below the last log line
277 to show work is not stalled.
279 Available when not in DEBUG log level.
281 config LOG_USE_COLORS
283 prompt "Use colors for logging to console"
286 Use colors to highlight important messages.
295 prompt "Log to a file"
298 Save *full* logs to a file. Even log levels you didn't specify above
299 will be available in this file.
301 As a bonus, there is a script in tools/extractConfig.sh that is able
302 to extract the configuration of crosstool-NG from the log file.
309 default "${CT_PREFIX_DIR}/${CT_TARGET}.log"
310 depends on LOG_TO_FILE
312 File name into which to put logs.