This adds the debug symbols for the binaries included in the uninative
tar ball. These are needed if one wants to run valgrind on a native
binary when uninative is used. Or get complete backtraces using gdb.
Signed-off-by: Peter Kjellerstedt <peter.kjellerst...@axis.com>
---
For the uninative tar ball for x86-64 that I built to test this change
the size increased by ~4% (200 kB). I hope that is acceptable to
consider this change.
meta/recipes-core/meta/uninative-tarball.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/meta/uninative-tarball.bb
b/meta/recipes-core/meta/uninative-tarball.bb
index c4a6c96b4d..bbdaebad94 100644
--- a/meta/recipes-core/meta/uninative-tarball.bb
+++ b/meta/recipes-core/meta/uninative-tarball.bb
@@ -8,6 +8,7 @@ TOOLCHAIN_TARGET_TASK = ""
# utf-16, cp1252 - binutils-windres
TOOLCHAIN_HOST_TASK = "\
nativesdk-glibc \
+ nativesdk-glibc-dbg \
nativesdk-glibc-gconv-ibm850 \
nativesdk-glibc-gconv-iso8859-1 \
nativesdk-glibc-gconv-utf-16 \
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#148568):
https://lists.openembedded.org/g/openembedded-core/message/148568
Mute This Topic: https://lists.openembedded.org/mt/80887323/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
