From: "Jan Kircher" <jan.kircher@leica-microsystems.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Proposal: skip debug builds of native packages
Date: Mon, 28 Apr 2025 00:52:03 -0700 [thread overview]
Message-ID: <8641.1745826723338154901@lists.openembedded.org> (raw)
In-Reply-To: <DB5PR02MB102139C9D2A02EE8499251479EFBD2@DB5PR02MB10213.eurprd02.prod.outlook.com>
On Wed, Apr 16, 2025 at 03:01 PM, Peter Kjellerstedt wrote:
> If you are setting DEBUG_BUILD globally rather than per recipe, then the
> solution for you to avoid enabling it for native recipes would be to
> instead use:
>
> DEBUG_BUILD:class-target = "1"
>
> //Peter
>
That is a way better solution. I didn't know this is possible. Thank you!
next prev parent reply other threads:[~2025-04-28 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 9:02 Proposal: skip debug builds of native packages Jan Kircher
2025-04-16 13:00 ` [OE-core] " Peter Kjellerstedt
2025-04-28 7:52 ` Jan Kircher [this message]
2025-04-22 14:56 ` Alexander Kanavin
2025-04-22 22:43 ` Khem Raj
2025-04-22 23:32 ` Alexander Kanavin
2025-04-23 0:38 ` Khem Raj
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=8641.1745826723338154901@lists.openembedded.org \
--to=jan.kircher@leica-microsystems.com \
--cc=openembedded-core@lists.openembedded.org \
/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