summaryrefslogtreecommitdiff
path: root/docs/busybox.net/FAQ.html
diff options
context:
space:
mode:
authorRob Landley2005-09-05 10:25:51 +0000
committerRob Landley2005-09-05 10:25:51 +0000
commitd1fa5859d60b246f5b345e921edbb86e31c41930 (patch)
tree9f8fac7f534493d9b65a528fd5fd39de1a72d818 /docs/busybox.net/FAQ.html
parentdbaf97e463a63062e0a1a7f98ee9ff564639fb58 (diff)
downloadbusybox-d1fa5859d60b246f5b345e921edbb86e31c41930.zip
busybox-d1fa5859d60b246f5b345e921edbb86e31c41930.tar.gz
Now that "make sizes" is in, the faq should mention it...
Diffstat (limited to 'docs/busybox.net/FAQ.html')
-rw-r--r--docs/busybox.net/FAQ.html16
1 files changed, 4 insertions, 12 deletions
diff --git a/docs/busybox.net/FAQ.html b/docs/busybox.net/FAQ.html
index 5090c41..67c696c 100644
--- a/docs/busybox.net/FAQ.html
+++ b/docs/busybox.net/FAQ.html
@@ -258,18 +258,10 @@ have additions to this FAQ document, we would love to add them,
savings add up).
</p>
<p>
- To examine a busybox binary with an eye to saving bytes, build an
- optimized debug version and run the "nm" command against it, like so:
-</p>
-<p>
- make clean && make STRIPCMD=/bin/true && nm --size-sort busybox
-</p>
-<p>
- This gives a list of symbols and the amount of space allocated for
- each one, sorted by size. (Note: do not enable CONFIG_DEBUG for this,
- as that disables compiler optimization which is great for running gdb
- but misleading when trying to figure out how much space each component
- is really using under normal circumstances.)
+ The busybox Makefile can generate a report of how much space is actually
+ being used by each function and variable. Run "<b>make sizes</b>" (preferably
+ with CONFIG_DEBUG off) to get a list of symbols and the amount of
+ space allocated for each one, sorted by size.
</p>
<hr />