yann@1
|
1 |
# Overall toolchain configuration: paths, jobs, etc...
|
yann@1
|
2 |
|
yann@1
|
3 |
menu "Paths and misc options"
|
yann@1
|
4 |
|
yann@1
|
5 |
config PARALLEL_JOBS
|
yann@1
|
6 |
int
|
yann@1
|
7 |
prompt "Number of parallel jobs"
|
yann@1
|
8 |
default 1
|
yann@1
|
9 |
help
|
yann@1
|
10 |
Number of jobs make will be allowed to run concurently.
|
yann@1
|
11 |
Set this higher than the number of processors you have, but not too high.
|
yann@1
|
12 |
A good rule of thumb is twice the number of processors you have.
|
yann@1
|
13 |
|
yann@1
|
14 |
Enter 1 (or 0) to have only one job at a time.
|
yann@1
|
15 |
|
yann@1
|
16 |
config LOAD
|
yann@1
|
17 |
int
|
yann@1
|
18 |
prompt "Maximum allowed load"
|
yann@1
|
19 |
default 0
|
yann@1
|
20 |
help
|
yann@1
|
21 |
Specifies that no new jobs should be started if there are others jobs
|
yann@1
|
22 |
running and the load average is at least this value.
|
yann@1
|
23 |
|
yann@1
|
24 |
Makes sense on SMP machines only.
|
yann@1
|
25 |
|
yann@1
|
26 |
Enter 0 to have no limit on the load average.
|
yann@1
|
27 |
|
yann@1
|
28 |
Note: only the integer part of the load is allowed here (you can't enter
|
yann@1
|
29 |
0.75 for example).
|
yann@1
|
30 |
|
yann@1
|
31 |
config NICE
|
yann@1
|
32 |
int
|
yann@1
|
33 |
prompt "Nice level"
|
yann@1
|
34 |
default 0
|
yann@1
|
35 |
range 0 19
|
yann@1
|
36 |
help
|
yann@1
|
37 |
Renices the build process up.
|
yann@1
|
38 |
|
yann@1
|
39 |
config USE_PIPES
|
yann@1
|
40 |
bool
|
yann@1
|
41 |
prompt "Use -pipe"
|
yann@1
|
42 |
default y
|
yann@1
|
43 |
help
|
yann@1
|
44 |
Use gcc's option -pipe to use pipes rather than temp files when building
|
yann@1
|
45 |
the toolchain.
|
yann@1
|
46 |
|
yann@1
|
47 |
comment "Paths"
|
yann@1
|
48 |
|
yann@1
|
49 |
config TARBALLS_DIR
|
yann@1
|
50 |
string
|
yann@1
|
51 |
prompt "Tarballs directory"
|
yann@1
|
52 |
default "`pwd`/tarballs"
|
yann@1
|
53 |
help
|
yann@1
|
54 |
This is the directory into which tarballs are going to be stored once
|
yann@1
|
55 |
they are downloaded (or otherwise retrieved).
|
yann@1
|
56 |
|
yann@1
|
57 |
config SRC_DIR
|
yann@1
|
58 |
string
|
yann@1
|
59 |
prompt "Extract directory"
|
yann@1
|
60 |
default "`pwd`/${CT_TARGET}/src"
|
yann@1
|
61 |
help
|
yann@1
|
62 |
This is the directory into which tarballs will be extracted.
|
yann@1
|
63 |
|
yann@1
|
64 |
If you will build multiple toolchains, you should arrange to have one
|
yann@1
|
65 |
SRC_DIR for each toolchain, as different targets may require different
|
yann@1
|
66 |
patches to be applied.
|
yann@1
|
67 |
|
yann@1
|
68 |
config BUILD_DIR
|
yann@1
|
69 |
string
|
yann@1
|
70 |
prompt "Build directory"
|
yann@1
|
71 |
default "`pwd`/${CT_TARGET}/gcc-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}"
|
yann@1
|
72 |
help
|
yann@1
|
73 |
This is the directory into which builds will occur.
|
yann@1
|
74 |
|
yann@1
|
75 |
Once again, arrange for one build directory for each toolchain you build,
|
yann@1
|
76 |
to avoid collision.
|
yann@1
|
77 |
|
yann@1
|
78 |
config PREFIX_DIR
|
yann@1
|
79 |
string
|
yann@1
|
80 |
prompt "Prefix directory"
|
yann@1
|
81 |
default "${HOME}/${CT_TARGET}"
|
yann@1
|
82 |
help
|
yann@1
|
83 |
This is the path the toolchain will run from.
|
yann@1
|
84 |
|
yann@1
|
85 |
config INSTALL_DIR
|
yann@1
|
86 |
string
|
yann@1
|
87 |
# prompt "Install directory"
|
yann@1
|
88 |
default "${CT_PREFIX_DIR}"
|
yann@1
|
89 |
# help
|
yann@1
|
90 |
# This is the path the target will be installed into.
|
yann@1
|
91 |
#
|
yann@1
|
92 |
# Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
|
yann@1
|
93 |
# you can't write there, you can install somewhere else and have a third
|
yann@1
|
94 |
# person do the install for you.
|
yann@1
|
95 |
# The reason you might also want to install elsewhere is if you are going
|
yann@1
|
96 |
# to package your shinny new toolchain for distribution.
|
yann@1
|
97 |
|
yann@1
|
98 |
config CUSTOM_PATCH
|
yann@1
|
99 |
bool
|
yann@1
|
100 |
prompt "Use custom patch directory"
|
yann@1
|
101 |
default n
|
yann@1
|
102 |
help
|
yann@1
|
103 |
If you have custom patches that you want to be applied, say 'Y' here and
|
yann@1
|
104 |
enter the path directory below.
|
yann@1
|
105 |
|
yann@1
|
106 |
Note that you must ensure that the patch directory is arranged the same
|
yann@1
|
107 |
way the official directory is.
|
yann@1
|
108 |
|
yann@1
|
109 |
config CUSTOM_PATCH_ONLY
|
yann@1
|
110 |
bool
|
yann@1
|
111 |
prompt "Only use custom patches"
|
yann@1
|
112 |
default n
|
yann@1
|
113 |
depends on CUSTOM_PATCH
|
yann@1
|
114 |
help
|
yann@1
|
115 |
Don't apply patches coming with CT-NG, only those patches available in
|
yann@1
|
116 |
the directory below.
|
yann@1
|
117 |
|
yann@1
|
118 |
If you say 'N' here, then the patches provided with CT-NG will be applied
|
yann@1
|
119 |
first, and then your patches.
|
yann@1
|
120 |
|
yann@1
|
121 |
config CUSTOM_PATCH_DIR
|
yann@1
|
122 |
string
|
yann@1
|
123 |
prompt "Custom patch directory"
|
yann@1
|
124 |
default ""
|
yann@1
|
125 |
depends on CUSTOM_PATCH
|
yann@1
|
126 |
help
|
yann@1
|
127 |
Enter the custom patch directory here.
|
yann@1
|
128 |
|
yann@14
|
129 |
config REMOVE_DOCS
|
yann@14
|
130 |
bool
|
yann@14
|
131 |
prompt "Remove documentation"
|
yann@14
|
132 |
default n
|
yann@14
|
133 |
help
|
yann@14
|
134 |
Remove the installed documentation (man and info pages).
|
yann@14
|
135 |
Gains around 8MiB for a uClibc-based, C and C++ compiler.
|
yann@14
|
136 |
|
yann@1
|
137 |
comment "Downloading and extracting"
|
yann@1
|
138 |
|
yann@1
|
139 |
config NO_DOWNLOAD
|
yann@1
|
140 |
bool
|
yann@1
|
141 |
prompt "Avoid downloads"
|
yann@1
|
142 |
default n
|
yann@1
|
143 |
help
|
yann@1
|
144 |
Avoid downloading anything. Bail out if a tarball is missing.
|
yann@1
|
145 |
|
yann@1
|
146 |
config ONLY_DOWNLOAD
|
yann@1
|
147 |
bool
|
yann@1
|
148 |
prompt "Only download tarballs"
|
yann@1
|
149 |
default n
|
yann@1
|
150 |
depends on ! NO_DOWNLOAD
|
yann@1
|
151 |
help
|
yann@1
|
152 |
Only download the tarballs. Exit once it done.
|
yann@1
|
153 |
|
yann@1
|
154 |
Usefull to pre-retrieve the tarballs before going off-line.
|
yann@1
|
155 |
|
yann@1
|
156 |
config FORCE_DOWNLOAD
|
yann@1
|
157 |
bool
|
yann@1
|
158 |
prompt "Force downloads"
|
yann@1
|
159 |
default n
|
yann@1
|
160 |
depends on ! NO_DOWNLOAD
|
yann@1
|
161 |
help
|
yann@1
|
162 |
Force downloading tarballs, even if one already exists.
|
yann@1
|
163 |
Usefull if you suspect a tarball to be damaged.
|
yann@1
|
164 |
|
yann@1
|
165 |
config FORCE_EXTRACT
|
yann@1
|
166 |
bool
|
yann@1
|
167 |
prompt "Force extractions"
|
yann@1
|
168 |
depends on ! ONLY_DOWNLOAD
|
yann@1
|
169 |
default n
|
yann@1
|
170 |
help
|
yann@1
|
171 |
Force extraction of already exctracted tarballs.
|
yann@1
|
172 |
|
yann@1
|
173 |
Usefull if you suspect a previous extract did not complete (eg. broken
|
yann@1
|
174 |
tarball), or you added a new set of patches for this component.
|
yann@1
|
175 |
|
yann@1
|
176 |
comment "Logging"
|
yann@1
|
177 |
|
yann@1
|
178 |
choice
|
yann@1
|
179 |
bool
|
yann@1
|
180 |
prompt "Maximum log level to see:"
|
yann@1
|
181 |
default LOG_INFO
|
yann@1
|
182 |
|
yann@1
|
183 |
config LOG_ERROR
|
yann@1
|
184 |
bool
|
yann@1
|
185 |
prompt "ERROR"
|
yann@1
|
186 |
help
|
yann@1
|
187 |
The build will be silent.
|
yann@1
|
188 |
Only if there is an error will you see a mesage.
|
yann@1
|
189 |
|
yann@1
|
190 |
config LOG_WARN
|
yann@1
|
191 |
bool
|
yann@1
|
192 |
prompt "WARN"
|
yann@1
|
193 |
help
|
yann@1
|
194 |
The same as above, plus warnings.
|
yann@1
|
195 |
|
yann@1
|
196 |
config LOG_INFO
|
yann@1
|
197 |
bool
|
yann@1
|
198 |
prompt "INFO"
|
yann@1
|
199 |
help
|
yann@1
|
200 |
The same as above, plus informational messages (main steps).
|
yann@1
|
201 |
|
yann@1
|
202 |
config LOG_EXTRA
|
yann@1
|
203 |
bool
|
yann@1
|
204 |
prompt "EXTRA"
|
yann@1
|
205 |
help
|
yann@1
|
206 |
The same as above, plus extra messages (sub-steps).
|
yann@1
|
207 |
|
yann@1
|
208 |
config LOG_DEBUG
|
yann@1
|
209 |
bool
|
yann@1
|
210 |
prompt "DEBUG"
|
yann@1
|
211 |
help
|
yann@1
|
212 |
The same as above, plus lots of debug information, of which each
|
yann@1
|
213 |
component's build messages (very noisy!).
|
yann@1
|
214 |
|
yann@1
|
215 |
endchoice
|
yann@1
|
216 |
|
yann@1
|
217 |
config LOG_LEVEL_MAX
|
yann@1
|
218 |
string
|
yann@1
|
219 |
default "ERROR" if LOG_ERROR
|
yann@1
|
220 |
default "WARN" if LOG_WARN
|
yann@1
|
221 |
default "INFO" if LOG_INFO
|
yann@1
|
222 |
default "EXTRA" if LOG_EXTRA
|
yann@1
|
223 |
default "DEBUG" if LOG_DEBUG
|
yann@1
|
224 |
|
yann@1
|
225 |
config LOG_PROGRESS_BAR
|
yann@1
|
226 |
bool
|
yann@1
|
227 |
prompt "Progress bar"
|
yann@1
|
228 |
default n
|
yann@1
|
229 |
depends on ! LOG_DEBUG
|
yann@1
|
230 |
help
|
yann@1
|
231 |
This option will print a "rotating bar" (/-\|) below the last log line
|
yann@1
|
232 |
to show work is not stalled.
|
yann@1
|
233 |
|
yann@1
|
234 |
Available when not in DEBUG log level.
|
yann@1
|
235 |
|
yann@1
|
236 |
config LOG_USE_COLORS
|
yann@1
|
237 |
bool
|
yann@1
|
238 |
prompt "Use colors for logging to console"
|
yann@1
|
239 |
default n
|
yann@1
|
240 |
help
|
yann@1
|
241 |
Use colors to highlight important messages.
|
yann@1
|
242 |
ERROR: bright red
|
yann@1
|
243 |
WARN : bright yellow
|
yann@1
|
244 |
INFO : bright green
|
yann@1
|
245 |
EXTRA: dim green
|
yann@1
|
246 |
DEBUG: dim white
|
yann@1
|
247 |
|
yann@1
|
248 |
config LOG_TO_FILE
|
yann@1
|
249 |
bool
|
yann@1
|
250 |
prompt "Log to a file"
|
yann@1
|
251 |
default y
|
yann@1
|
252 |
help
|
yann@1
|
253 |
Save *full* logs to a file. Even log levels you didn't specify above
|
yann@1
|
254 |
will be available in this file.
|
yann@1
|
255 |
|
yann@1
|
256 |
config LOG_FILE
|
yann@1
|
257 |
string
|
yann@1
|
258 |
prompt "Log file"
|
yann@1
|
259 |
default "${CT_PREFIX_DIR}/${CT_TARGET}.log"
|
yann@1
|
260 |
depends on LOG_TO_FILE
|
yann@1
|
261 |
help
|
yann@1
|
262 |
File name into which to put logs.
|
yann@1
|
263 |
|
yann@1
|
264 |
endmenu
|