summaryrefslogtreecommitdiff
path: root/busybox/docs
diff options
context:
space:
mode:
authorRob Landley <rob@landley.net>2005-08-13 01:10:27 +0000
committerRob Landley <rob@landley.net>2005-08-13 01:10:27 +0000
commitbe3dae145f71b583f2c975d8dcdc10d9dad2268a (patch)
tree4bcd50be61a1945e41eabd59d645d398fc038522 /busybox/docs
parent6022fc8723c4bfaf055011db33f69565fa0c82b1 (diff)
downloadbusybox-w32-be3dae145f71b583f2c975d8dcdc10d9dad2268a.tar.gz
busybox-w32-be3dae145f71b583f2c975d8dcdc10d9dad2268a.tar.bz2
busybox-w32-be3dae145f71b583f2c975d8dcdc10d9dad2268a.zip
Makefile related backports:
10945, 10946 Make compile much, much faster. 10923 big makefile change. Nervous. 10946, 10991, 10998, 11003 small makefile fixes.
Diffstat (limited to 'busybox/docs')
-rw-r--r--busybox/docs/busybox.net/FAQ.html87
1 files changed, 26 insertions, 61 deletions
diff --git a/busybox/docs/busybox.net/FAQ.html b/busybox/docs/busybox.net/FAQ.html
index a9324ae26..8de06e632 100644
--- a/busybox/docs/busybox.net/FAQ.html
+++ b/busybox/docs/busybox.net/FAQ.html
@@ -254,68 +254,33 @@ have additions to this FAQ document, we would love to add them,
254 trust PayPal... 254 trust PayPal...
255 255
256<hr /> 256<hr />
257<p>
258<h2><a name="optimize">I want to make busybox even smaller, how do I go about it?</a></h2>
259<p>
260 To conserve bytes it's good to know where they're being used, and the
261 size of the final executable isn't always a reliable indicator of
262 the size of the components (since various structures are rounded up,
263 so a small change may not even be visible by itself, but many small
264 savings add up).
265</p>
266<p>
267 To examine a busybox binary with an eye to saving bytes, build an
268 optimized debug version and run the "nm" command against it, like so:
269</p>
270<p>
271 make clean && make STRIPCMD=/bin/true && nm --size-sort busybox
272</p>
273<p>
274 This gives a list of symbols and the amount of space allocated for
275 each one, sorted by size. (Note: do not enable CONFIG_DEBUG for this,
276 as that disables compiler optimization which is great for running gdb
277 but misleading when trying to figure out how much space each component
278 is really using under normal circumstances.)
279</p>
280<hr />
281
282
257 283
258<br>
259<br>
260<br>
261<br>
262<br>
263<br>
264<br>
265<br>
266<br>
267<br>
268<br>
269<br>
270<br>
271<br>
272<br>
273<br>
274<br>
275<br>
276<br>
277<br>
278<br>
279<br>
280<br>
281<br>
282<br>
283<br>
284<br>
285<br>
286<br>
287<br>
288<br>
289<br>
290<br>
291<br>
292<br>
293<br>
294<br>
295<br>
296<br>
297<br>
298<br>
299<br>
300<br>
301<br>
302<br>
303<br>
304<br>
305<br>
306<br>
307<br>
308<br>
309<br>
310<br>
311<br>
312<br>
313<br>
314<br>
315<br>
316<br>
317<br>
318<br>
319<br> 284<br>
320<br> 285<br>
321<br> 286<br>