On Tue, 18 May 2021, Andre McCurdy wrote:
> On Tue, May 18, 2021 at 10:00 AM Robert P. J. Day <rpj...@crashcourse.ca>
> wrote:
> > 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}/*
>
> Did that actually help with the image size?
reportedly, it did, but the installation process being used in this
case is decidedly non-standard and does some interesting end runs
around normal YP processing so i'm not putting much stock in that.
> > 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.
>
> Yes, if you remove debug symbols before packaging then they won't be
> available to put in the -dbg packages.
which is exactly what i suspected ... i'm poking around the code
right now to understand it better.
> > 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
>
> Isn't that what happens by default?
that's what i've come to understand but, again, the installation and
packaging process here is a little unusual and could be bypassing all
sorts of normal YP processing.
> > 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"
>
> This came up on the list a few months ago. Enabling every possible
> option somehow related to debug as advised by stack overflow probably
> isn't the best approach.
i already figured out that the above was simply an example of one
approach, and not the one i wanted. but i think i'm converging on a
solution.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152038):
https://lists.openembedded.org/g/openembedded-core/message/152038
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]
-=-=-=-=-=-=-=-=-=-=-=-
