In most cases you want to debug target binaries, or native, or cross
but it would be unusual to want to do all at the same time.

Drop DEBUG_BUILD, and set INHIBIT_SYSROOT_STRIP ??= "" by default,
user could use ?= to override in local.conf if needed

Suggested-by: Richard Purdie <[email protected]>
Signed-off-by: Hongxu Jia <[email protected]>
---
 meta/classes-recipe/cross.bbclass  | 3 +--
 meta/classes-recipe/native.bbclass | 3 +--
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/meta/classes-recipe/cross.bbclass 
b/meta/classes-recipe/cross.bbclass
index c3eeade67b..574ce6988d 100644
--- a/meta/classes-recipe/cross.bbclass
+++ b/meta/classes-recipe/cross.bbclass
@@ -23,8 +23,7 @@ HOST_CC_ARCH = "${BUILD_CC_ARCH}"
 HOST_LD_ARCH = "${BUILD_LD_ARCH}"
 HOST_AS_ARCH = "${BUILD_AS_ARCH}"
 
-# No strip sysroot when DEBUG_BUILD is enabled
-INHIBIT_SYSROOT_STRIP ?= "${@oe.utils.vartrue('DEBUG_BUILD', '1', '', d)}"
+INHIBIT_SYSROOT_STRIP ??= ""
 
 export lt_cv_sys_lib_dlsearch_path_spec = "${libdir} ${base_libdir} /lib 
/lib64 /usr/lib /usr/lib64"
 
diff --git a/meta/classes-recipe/native.bbclass 
b/meta/classes-recipe/native.bbclass
index 7d1fe343fa..b3411d20ca 100644
--- a/meta/classes-recipe/native.bbclass
+++ b/meta/classes-recipe/native.bbclass
@@ -118,8 +118,7 @@ PATH:prepend = "${COREBASE}/scripts/native-intercept:"
 # reused if we manipulate the paths.
 SSTATE_SCAN_CMD ?= "${SSTATE_SCAN_CMD_NATIVE}"
 
-# No strip sysroot when DEBUG_BUILD is enabled
-INHIBIT_SYSROOT_STRIP ?= "${@oe.utils.vartrue('DEBUG_BUILD', '1', '', d)}"
+INHIBIT_SYSROOT_STRIP ??= ""
 
 python native_virtclass_handler () {
     import re
-- 
2.34.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#228057): 
https://lists.openembedded.org/g/openembedded-core/message/228057
Mute This Topic: https://lists.openembedded.org/mt/116827531/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to