|author||Roman Khimov <email@example.com>||2010-04-18 22:41:40 +0000|
|committer||Roman I Khimov <firstname.lastname@example.org>||2010-04-25 17:13:15 +0400|
change INHIBIT_PACKAGE_STRIP to PACKAGE_STRIP with more options
Originally approached with "package.bbclass: introduce KEEP_GNU_DEBUGLINK": http://patchwork.openembedded.org/patch/886/ Redone with a change from INHIBIT_PACKAGE_STRIP to PACKAGE_STRIP which allows more options. By default it does exactly the same thing as is done today, strips the binary, but keeps the gnu.debuglink section. When set to "no", stripping is not done at all, when set to "full" the gnu.debuglink section is not re-added to the binary. Signed-off-by: Roman I Khimov <email@example.com> Acked-by: Chris Larson <firstname.lastname@example.org>
Diffstat (limited to 'conf/local.conf.sample')
1 files changed, 11 insertions, 4 deletions
diff --git a/conf/local.conf.sample b/conf/local.conf.sample
index 2cff53bc1b..af20c93254 100644
@@ -124,11 +124,18 @@ IMAGE_FSTYPES = "jffs2 tar"
# Uncomment this if you want BitBake to emit debugging output
# BBDEBUG = "yes"
-# Uncomment these two if you want BitBake to build images useful for debugging.
-# Note that INHIBIT_PACKAGE_STRIP needs a package format to be defined.
-# Also note that OE now produces -dbg packages which contain debugging symbols.
+# Use DEBUG_BUILD to build packages with DEBUG_OPTIMIZATION instead of
# DEBUG_BUILD = "1"
-# INHIBIT_PACKAGE_STRIP = "1"
+# If you want to have unstripped ready-to-debug binaries, set this to "no",
+# although for debugging you can use automatically produced -dbg packages.
+# If you need to have completely undebuggable builds, set this to "full",
+# by default gnu.debuglink section is left in the binaries after stripping, so
+# this might be useful if you want to have checksum-level binary consistency
+# across successive builds.
+# PACKAGE_STRIP = "no"
# Uncomment these to build a package such that you can use gprof to profile it.
# NOTE: This will only work with 'linux' targets, not