Add the EXPERIMENTAL option to show options marked as such.
Add the four types of toolchains ct-ng is able to build as EXPERIMENTAL, except for CROSS which *is* functional.
Reorder menus accordingly.
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 "Number of parallel jobs"
24 Number of jobs make will be allowed to run concurently.
25 Set this higher than the number of processors you have, but not too high.
26 A good rule of thumb is twice the number of processors you have.
28 Enter 1 (or 0) to have only one job at a time.
32 prompt "Maximum allowed load"
35 Specifies that no new jobs should be started if there are others jobs
36 running and the load average is at least this value.
38 Makes sense on SMP machines only.
40 Enter 0 to have no limit on the load average.
42 Note: only the integer part of the load is allowed here (you can't enter
51 Renices the build process up.
58 Use gcc's option -pipe to use pipes rather than temp files when building
65 prompt "Tarballs directory"
66 default "${CT_TOP_DIR}/build/tarballs"
68 This is the directory into which tarballs are going to be stored once
69 they are downloaded (or otherwise retrieved).
73 prompt "Extract directory"
74 default "${CT_TOP_DIR}/build/${CT_TARGET}/${CT_CC}-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}/src"
76 This is the directory into which tarballs will be extracted.
78 If you will build multiple toolchains, you should arrange to have one
79 SRC_DIR for each toolchain, as different targets may require different
80 patches to be applied.
82 You should not need to change this from the default.
86 prompt "Build directory"
87 default "${CT_TOP_DIR}/build/${CT_TARGET}/${CT_CC}-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}/build"
89 This is the directory into which builds will occur.
91 Once again, arrange for one build directory for each toolchain you build,
94 You should not need to change this from the default.
98 prompt "Prefix directory"
99 default "${HOME}/${CT_TARGET}"
101 This is the path the toolchain will run from.
105 # prompt "Install directory"
106 default "${CT_PREFIX_DIR}"
108 # This is the path the target will be installed into.
110 # Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
111 # you can't write there, you can install somewhere else and have a third
112 # person do the install for you.
113 # The reason you might also want to install elsewhere is if you are going
114 # to package your shinny new toolchain for distribution.
118 prompt "Use custom patch directory"
121 If you have custom patches that you want to be applied, say 'Y' here and
122 enter the path directory below.
124 Note that you must ensure that the patch directory is arranged the same
125 way the official directory is.
127 config CUSTOM_PATCH_ONLY
129 prompt "Only use custom patches"
131 depends on CUSTOM_PATCH
133 Don't apply patches coming with CT-NG, only those patches available in
136 If you say 'N' here, then the patches provided with CT-NG will be applied
137 first, and then your patches.
139 config CUSTOM_PATCH_DIR
141 prompt "Custom patch directory"
143 depends on CUSTOM_PATCH
145 Enter the custom patch directory here.
149 prompt "Remove documentation"
152 Remove the installed documentation (man and info pages).
153 Gains around 8MiB for a uClibc-based, C and C++ compiler.
155 comment "Downloading and extracting"
159 prompt "Avoid downloads"
162 Avoid downloading anything. Bail out if a tarball is missing.
166 prompt "Only download tarballs"
168 depends on ! NO_DOWNLOAD
170 Only download the tarballs. Exit once it done.
172 Usefull to pre-retrieve the tarballs before going off-line.
174 config FORCE_DOWNLOAD
176 prompt "Force downloads"
178 depends on ! NO_DOWNLOAD
180 Force downloading tarballs, even if one already exists.
181 Usefull if you suspect a tarball to be damaged.
185 prompt "Force extractions"
186 depends on ! ONLY_DOWNLOAD
189 Force extraction of already exctracted tarballs.
191 Usefull if you suspect a previous extract did not complete (eg. broken
192 tarball), or you added a new set of patches for this component.
198 prompt "Maximum log level to see:"
205 The build will be silent.
206 Only if there is an error will you see a mesage.
212 The same as above, plus warnings.
218 The same as above, plus informational messages (main steps).
224 The same as above, plus extra messages (sub-steps).
230 The same as above, plus lots of debug information, of which each
231 component's build messages (very noisy!).
237 default "ERROR" if LOG_ERROR
238 default "WARN" if LOG_WARN
239 default "INFO" if LOG_INFO
240 default "EXTRA" if LOG_EXTRA
241 default "DEBUG" if LOG_DEBUG
243 config LOG_PROGRESS_BAR
245 prompt "Progress bar"
247 depends on ! LOG_DEBUG
249 This option will print a "rotating bar" (/-\|) below the last log line
250 to show work is not stalled.
252 Available when not in DEBUG log level.
254 config LOG_USE_COLORS
256 prompt "Use colors for logging to console"
259 Use colors to highlight important messages.
268 prompt "Log to a file"
271 Save *full* logs to a file. Even log levels you didn't specify above
272 will be available in this file.
277 default "${CT_PREFIX_DIR}/${CT_TARGET}.log"
278 depends on LOG_TO_FILE
280 File name into which to put logs.