d1fa5859d
Rob Landley
2005-09-05
Subject
Now that "make sizes" is in, the faq should mention it...
SOURCE BUG
This commit was genuinely broken at the time (not related to our build system): scripts/config/mkconfigs.c (2005-08-01 - 2006-10-05 arasi) uretilen bbconfigopts.h icine .config satirlarini kacissiz, ham newline'larla gömüyordu - gecerli C degildi, busybox'un kendi bb_mkdep araci bile parse edemiyordu (7d219aab7 ile duzeltildi, mkconfigs shell scripte cevrildi)
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
docs/busybox.net/FAQ.html+4 -12
| @@ -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 /> | |