public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v6 1/8] distro/include: rework debug build
Date: Sun, 21 Dec 2025 23:09:57 +0000	[thread overview]
Message-ID: <67c01b7bbde3068d136b15d3855e3bef11a96990.camel@linuxfoundation.org> (raw)
In-Reply-To: <20251217152421.1181080-1-hongxu.jia@windriver.com>

On Wed, 2025-12-17 at 23:24 +0800, Hongxu Jia wrote:
> The problem with DEBUG_BUILD is that we have a lot of debug information
> in builds anyway and this is now unclear what it means. The
> documentation.conf entry mentions packages which is now incorrect too.
> The variable is a very old one and the interface is poorly designed
> compared to other areas now.
> 
> This commit drop DEBUG_BUILD, and add debug_build.inc to instead.
> In bitbake.conf, use ??= to set *_OPTIMIZATION, in debug_build.inc to
> use ?= to override *_OPTIMIZATION
> 
> Make a config fragment to use include_all debug_build.inc to allow other
> layers to add their own debug build configurations, user should use the
> following ways to enable debug build
> 
>   $ bitbake-config-build enable-fragment core/yocto/debug-build
> 
> Or
> 
>   $ echo 'OE_FRAGMENTS += "core/yocto/debug-build"' >> conf/local.conf
> 
> Suggested-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Suggested-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>

Thanks, this series does look much better, I was really happy to see it
and I really wanted to merge it.

Unfortunately, Peter does have a point that this makes it hard to
change this on a per recipe basis and that is a valid use case. I think
we may need to work out how to address that.

I also still don't like the name "debug-build" when it really means
"build without compiler optimisations". I think we need to find a
better name too...

Cheers,

Richard


  parent reply	other threads:[~2025-12-21 23:10 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 ` Richard Purdie [this message]
2025-12-22 11:32   ` [PATCH v6 1/8] distro/include: rework debug build hongxu

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=67c01b7bbde3068d136b15d3855e3bef11a96990.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=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