aboutsummaryrefslogtreecommitdiff
path: root/Config.in
diff options
context:
space:
mode:
authorRob Landley <rob@landley.net>2006-05-09 22:08:56 +0000
committerRob Landley <rob@landley.net>2006-05-09 22:08:56 +0000
commitc503df5bdda79ee9ed755325c0d76350a7a719c8 (patch)
treede6d49c010d80fc41028bf9ca7ef3872c30a4e18 /Config.in
parent2431830018a3cb789af0793647d7ba3db31d72f2 (diff)
downloadbusybox-c503df5bdda79ee9ed755325c0d76350a7a719c8.tar.gz
Split CONFIG_DEBUG from CONFIG_DEBUG_PESSIMIZE, and consolidate some Rules.mak
stuff along the way.
Diffstat (limited to 'Config.in')
-rw-r--r--Config.in22
1 files changed, 16 insertions, 6 deletions
diff --git a/Config.in b/Config.in
index 6dd4c58e7..bdc4b0a4f 100644
--- a/Config.in
+++ b/Config.in
@@ -288,17 +288,27 @@ endmenu
menu 'Debugging Options'
config CONFIG_DEBUG
- bool "Build BusyBox with Debugging symbols"
+ bool "Build BusyBox with extra Debugging symbols"
default n
help
- Say Y here if you wish to compile BusyBox with debugging symbols.
- This will allow you to use a debugger to examine BusyBox internals
- while applets are running. This increases the size of the binary
- considerably and should only be used when doing development.
- If you are doing development and want to debug BusyBox, answer Y.
+ Say Y here if you wish to examine BusyBox internals while applets are
+ running. This increases the size of the binary considerably, and
+ should only be used when doing development. If you are doing
+ development and want to debug BusyBox, answer Y.
Most people should answer N.
+config CONFIG_DEBUG_PESSIMIZE
+ bool "Disable compiler optimizations."
+ default n
+ depends on CONFIG_DEBUG
+ help
+ The compiler's optimization of source code can eliminate and reorder
+ code, resulting in an executable that's hard to understand when
+ stepping through it with a debugger. This switches it off, resulting
+ in a much bigger executable that more closely matches the source
+ code.
+
choice
prompt "Additional debugging library"
default CONFIG_NO_DEBUG_LIB