Now that "make sizes" is in, the faq should mention it...

git-svn-id: svn://busybox.net/trunk/busybox@11328 69ca8d6d-28ef-0310-b511-8ec308f3f277

1 files changed, 4 insertions, 12 deletions

diff --git a/docs/busybox.net/FAQ.html b/docs/busybox.net/FAQ.html
index 5090c41c2..67c696c4c 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 />