Closed ryanwoodsmall closed 5 years ago
Interesting! I did some size comparisons, and here's my results:
busybox:uclibc
image ~1.16MB, tarball ~616KBCONFIG_BBCONFIG
: image ~1.22MB, tarball ~624KBAny idea why this isn't enabled by default in defconfig
? Do you know whether upstream BusyBox maintainers officially recommend either including it or not including it? (I can't seem to find a lot of good info about it other than it exists. :sweat_smile:)
Upstream is pretty conservative about time/space tradeoffs. Best (only?) documentation is the source, but it doesn't have a ton of reasoning on defaults: https://git.busybox.net/busybox/tree/miscutils/bbconfig.c
In thinking about this more, I'm inclined to think this isn't really worth the additional size (even if it's small), since the things we enable above make defconfig
are already quite minimal:
Agreed. Closing. Thanks all!
BusyBox supports a sort of reflective applet called "bbconfig" which will dump the .config used while building the binary. This can be enabled with these config options:
This is a nicety but it's pretty useful when attempting to debug an issue with a container, the binary itself, etc.