Add an option to remove the generated documentation.
(After an idea from Enrico Weigelt <weigelt@metux.de>).
1 # Overall toolchain configuration: paths, jobs, etc...
3 menu "Paths and misc options"
7 prompt "Number of parallel jobs"
10 Number of jobs make will be allowed to run concurently.
11 Set this higher than the number of processors you have, but not too high.
12 A good rule of thumb is twice the number of processors you have.
14 Enter 1 (or 0) to have only one job at a time.
18 prompt "Maximum allowed load"
21 Specifies that no new jobs should be started if there are others jobs
22 running and the load average is at least this value.
24 Makes sense on SMP machines only.
26 Enter 0 to have no limit on the load average.
28 Note: only the integer part of the load is allowed here (you can't enter
37 Renices the build process up.
44 Use gcc's option -pipe to use pipes rather than temp files when building
51 prompt "Tarballs directory"
52 default "`pwd`/tarballs"
54 This is the directory into which tarballs are going to be stored once
55 they are downloaded (or otherwise retrieved).
59 prompt "Extract directory"
60 default "`pwd`/${CT_TARGET}/src"
62 This is the directory into which tarballs will be extracted.
64 If you will build multiple toolchains, you should arrange to have one
65 SRC_DIR for each toolchain, as different targets may require different
66 patches to be applied.
70 prompt "Build directory"
71 default "`pwd`/${CT_TARGET}/gcc-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}"
73 This is the directory into which builds will occur.
75 Once again, arrange for one build directory for each toolchain you build,
80 prompt "Prefix directory"
81 default "${HOME}/${CT_TARGET}"
83 This is the path the toolchain will run from.
87 # prompt "Install directory"
88 default "${CT_PREFIX_DIR}"
90 # This is the path the target will be installed into.
92 # Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
93 # you can't write there, you can install somewhere else and have a third
94 # person do the install for you.
95 # The reason you might also want to install elsewhere is if you are going
96 # to package your shinny new toolchain for distribution.
100 prompt "Use custom patch directory"
103 If you have custom patches that you want to be applied, say 'Y' here and
104 enter the path directory below.
106 Note that you must ensure that the patch directory is arranged the same
107 way the official directory is.
109 config CUSTOM_PATCH_ONLY
111 prompt "Only use custom patches"
113 depends on CUSTOM_PATCH
115 Don't apply patches coming with CT-NG, only those patches available in
118 If you say 'N' here, then the patches provided with CT-NG will be applied
119 first, and then your patches.
121 config CUSTOM_PATCH_DIR
123 prompt "Custom patch directory"
125 depends on CUSTOM_PATCH
127 Enter the custom patch directory here.
131 prompt "Remove documentation"
134 Remove the installed documentation (man and info pages).
135 Gains around 8MiB for a uClibc-based, C and C++ compiler.
137 comment "Downloading and extracting"
141 prompt "Avoid downloads"
144 Avoid downloading anything. Bail out if a tarball is missing.
148 prompt "Only download tarballs"
150 depends on ! NO_DOWNLOAD
152 Only download the tarballs. Exit once it done.
154 Usefull to pre-retrieve the tarballs before going off-line.
156 config FORCE_DOWNLOAD
158 prompt "Force downloads"
160 depends on ! NO_DOWNLOAD
162 Force downloading tarballs, even if one already exists.
163 Usefull if you suspect a tarball to be damaged.
167 prompt "Force extractions"
168 depends on ! ONLY_DOWNLOAD
171 Force extraction of already exctracted tarballs.
173 Usefull if you suspect a previous extract did not complete (eg. broken
174 tarball), or you added a new set of patches for this component.
180 prompt "Maximum log level to see:"
187 The build will be silent.
188 Only if there is an error will you see a mesage.
194 The same as above, plus warnings.
200 The same as above, plus informational messages (main steps).
206 The same as above, plus extra messages (sub-steps).
212 The same as above, plus lots of debug information, of which each
213 component's build messages (very noisy!).
219 default "ERROR" if LOG_ERROR
220 default "WARN" if LOG_WARN
221 default "INFO" if LOG_INFO
222 default "EXTRA" if LOG_EXTRA
223 default "DEBUG" if LOG_DEBUG
225 config LOG_PROGRESS_BAR
227 prompt "Progress bar"
229 depends on ! LOG_DEBUG
231 This option will print a "rotating bar" (/-\|) below the last log line
232 to show work is not stalled.
234 Available when not in DEBUG log level.
236 config LOG_USE_COLORS
238 prompt "Use colors for logging to console"
241 Use colors to highlight important messages.
250 prompt "Log to a file"
253 Save *full* logs to a file. Even log levels you didn't specify above
254 will be available in this file.
259 default "${CT_PREFIX_DIR}/${CT_TARGET}.log"
260 depends on LOG_TO_FILE
262 File name into which to put logs.