public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "hongxu" <hongxu.jia@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v6 1/8] distro/include: rework debug build
Date: Mon, 22 Dec 2025 03:32:51 -0800	[thread overview]
Message-ID: <281863.1766403171363602103@lists.openembedded.org> (raw)
In-Reply-To: <67c01b7bbde3068d136b15d3855e3bef11a96990.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 970 bytes --]

Understood

Due to option toolchain option `-Og' is the optimization for debugging[1]
how about rename debug-build to debug-optimize?

Drop DEBUG_BUILD, use DEBUG_OPTIMIZE to instead, add debug-optimize.bbclass
and debug-optimize.inc. Use variable DEBUG_OPTIMIZE to defer inherit
debug-optimize.bbclass conditionally.(Similar did in v5)

Make a config fragment core/yocto/debug-optimize to set DEBUG_OPTIMIZE ?= 1
to enable debug friendly optimize. For the recipe (such as qemu) which doesn't
work with debug optimization, set DEBUG_OPTIMIZE = "0" to disable it for a
given recipe even though config fragment core/yocto/debug-optimize is enabled

Do not encourage user to enable debug friendly optimization by setting
DEBUG_OPTIMIZE = '1' directly, because the variable override is not certainty,
which is affected by the order of configuration parsing

V7 incoming

[1] https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-Og

//Hongxu

[-- Attachment #2: Type: text/html, Size: 1342 bytes --]

      reply	other threads:[~2025-12-22 11:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 15:24 [PATCH v6 1/8] distro/include: rework debug build Hongxu Jia
2025-12-17 15:24 ` [PATCH v6 2/8] debug_build.inc: collect debug build tuning configuration Hongxu Jia
2025-12-17 15:24 ` [PATCH v6 3/8] {cross,native}.bbclass: drop DEBUG_BUILD Hongxu Jia
2025-12-17 15:24 ` [PATCH v6 4/8] debug_build.inc: override MESON_BUILDTYPE for target Hongxu Jia
2025-12-17 15:24 ` [PATCH v6 5/8] debug_build.inc: override CARGO_BUILD_MODE and CARGO_BUILD_DIR " Hongxu Jia
2025-12-17 15:24 ` [PATCH v6 6/8] debug_build.inc: disable debug build for qemu Hongxu Jia
2025-12-17 15:24 ` [PATCH v6 7/8] Clean up compiler optimization variable FULL_OPTIMIZATION Hongxu Jia
2025-12-17 15:24 ` [PATCH v6 8/8] Clean up compiler optimization variable DEBUG_OPTIMIZATION Hongxu Jia
2025-12-21 23:09 ` [PATCH v6 1/8] distro/include: rework debug build Richard Purdie
2025-12-22 11:32   ` hongxu [this message]

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=281863.1766403171363602103@lists.openembedded.org \
    --to=hongxu.jia@windriver.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