muh colleague just presented me with the following ... until
recently, build was properly producing bootable image while
simultaneously creating companion debugfs. so far, so good.
then enough packages were added so that image didn't fit in target
eMMC, so decision was made to strip bins and libs in ${D} image/
directory via sneaking the following into do_install_append():
${STRIP} -p --strip-unneeded ${D}${bindir}/*
${STRIP} -p --strip-unneeded ${D}${libdir}/*
as soon as this kicked in, the complaint was that numerous objects
were now missing from the debugfs, and i *suspect* (working to
confirm) that, having stripped all those binaries and libraries before
the packaging step kicks in, a lot of stuff that would have ended up
in the debugfs is now bypassed since it lacks the appropriate
debugging info anymore.
i'm looking at the various variables to see what would support:
1) stripping image-bound bins and libs, while
2) retaining debugging info to build debugfs
a stack overflow page suggests something like:
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"
DEBUG_BUILD = "1"
EXTRA_IMAGE_FEATURES_append = " dbg-pkgs"
but i'm open to what to set to get the desired effect.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152035):
https://lists.openembedded.org/g/openembedded-core/message/152035
Mute This Topic: https://lists.openembedded.org/mt/82916837/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
