From: Mathieu Othacehe <othacehe@gnu.org>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] lib/oe/package: Add debug_frame support
Date: Wed, 22 Jan 2025 21:01:38 +0100 [thread overview]
Message-ID: <87zfjiobx9.fsf@gnu.org> (raw)
In-Reply-To: <c80fe68f-2045-47c0-a2e8-076f23afcb3c@cherry.de> (Quentin Schulz's message of "Mon, 13 Jan 2025 15:07:50 +0100")
Hello Quentin,
Thanks for having a look!
> Would be nice to document this variable in the yocto-docs
> (https://git.yoctoproject.org/yocto-docs/). Would you mind sending us a patch
> once this lands (or if there's a v2, maybe alongside or at the same time?)?
> That would be for the variable glossary at the very least. Thanks!
Sure, I will send a documentation patch right after that one is merged.
> thought: would there be a use-case for keeping other sections?
>
> Therefore, instead of having multiple PACKAGE_KEEP_xxx variables, should we
> have PACKAGE_KEEP_SECTION = ".debug_frame"?
I guess you are right, and being able to keep some specific sections
besides .debug_frame can prove to be helpful in the future. I will
rework a bit this commit in that direction.
I think it would still be interesting to have a PACKAGE_KEEP_DEBUG_FRAME
variable around because that is more convenient for the user than
PACKAGE_KEEP_SECTION = ".debug_frame".
However, we can maybe keep both, by doing something like:
if bb.utils.to_boolean(d.getVar("PACKAGE_KEEP_DEBUG_FRAME"))
d.appendVar("PACKAGE_KEEP_SECTION", ".debug_frame")
Would that be OK?
Thanks,
Mathieu
next prev parent reply other threads:[~2025-01-22 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 7:39 [PATCH] lib/oe/package: Add debug_frame support Mathieu Othacehe
2025-01-13 14:07 ` [OE-core] " Quentin Schulz
2025-01-22 20:01 ` Mathieu Othacehe [this message]
2025-01-23 9:37 ` Quentin Schulz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfjiobx9.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@cherry.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox