From: "hongxu" <hongxu.jia@eng.windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 5/8] debug_build.inc: allow other layers to add their own debug build configurations
Date: Mon, 15 Sep 2025 20:59:17 -0700 [thread overview]
Message-ID: <20091.1757995157141119644@lists.openembedded.org> (raw)
In-Reply-To: <DB5PR02MB102130BB32912B2554180F776EF14A@DB5PR02MB10213.eurprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]
On Mon, Sep 15, 2025 at 05:25 PM, Peter Kjellerstedt wrote:
>
>
>> diff --git a/meta/conf/distro/include/debug_build.inc
>> b/meta/conf/distro/include/debug_build.inc
>> index 43d5ae59d53..f594df4b107 100644
>> --- a/meta/conf/distro/include/debug_build.inc
>> +++ b/meta/conf/distro/include/debug_build.inc
>> @@ -43,3 +43,6 @@ EXTRA_OECONF:append:pn-nativesdk-debugedit = "
>> --disable-inlined-xxhash"
>> lcl_maybe_fortify:pn-vim = ""
>>
>> CXXFLAGS:append:pn-vulkan-validation-layers = " -DXXH_NO_INLINE_HINTS=1"
>> +
>> +# Allow other layers to add their own debug build configurations
>> +include_all conf/include/debug_build.inc
>
> I think it is a bad idea to have this file in
> conf/distro/include/debug_build.inc
> and then expect other layers to have it in conf/include/debug_build.inc.
> That is
> bound to result in confusing mistakes. However, since you said that you
> could not
> use the include_all in bitbake.conf as you got an error due to the
> conditional
> include, I took a look at it. From what I can tell, the fact that you get
> an
> error is due to a bug in include_all, where it does not behave like
> include and
> require do when it comes to empty variable expansions.
>
> I have sent a stack of changes to the bitbake list that corrects the
> behavior for
> include_all so it works like include and require do. With that applied,
> you should
> be able to use the include_all directly in bitbake.conf instead.
I will move it to original meta/conf/bitbake.conf,
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -830,7 +830,9 @@ include conf/licenses.conf
require conf/sanity.conf
include conf/bblock.conf
-require ${@oe.utils.vartrue('DEBUG_BUILD', 'conf/distro/include/debug_build.inc', '', d)}
+# Allow other layers to add their own debug build configurations
+include_all ${@oe.utils.vartrue('DEBUG_BUILD', 'conf/distro/include/debug_build.inc', '', d)}
But as you said, it depends on bitbake commit [1] merged, so I still keep it as a standalone patch
[1] https://lists.openembedded.org/g/bitbake-devel/message/18037?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3ACreated%2C%2C%2C20%2C2%2C0%2C115265193%2Cd%253D3&d=3
//Hongxu
>
>
>> --
>> 2.34.1
>
>
[-- Attachment #2: Type: text/html, Size: 2723 bytes --]
next prev parent reply other threads:[~2025-09-16 3:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 6:17 [PATCH 1/8] yocto-space-optimize.inc: move space optimize from recipe webkitgtk Hongxu Jia
2025-09-15 6:17 ` [PATCH v2 2/8] distro/include: Add debug_build.inc when DEBUG_BUILD is enabled Hongxu Jia
2025-09-16 0:25 ` [OE-core] " Peter Kjellerstedt
2025-09-16 3:51 ` hongxu
2025-09-15 6:17 ` [PATCH v2 3/8] harfbuzz: set FULL_OPTLEVEL for FULL_OPTIMIZATION Hongxu Jia
2025-09-15 6:17 ` [PATCH v2 4/8] debug_build.inc: collect debug build tuning configuration Hongxu Jia
2025-09-15 6:17 ` [PATCH v2 5/8] debug_build.inc: allow other layers to add their own debug build configurations Hongxu Jia
2025-09-16 0:25 ` [OE-core] " Peter Kjellerstedt
2025-09-16 3:59 ` hongxu [this message]
2025-09-15 6:17 ` [PATCH 6/8] debug_build.inc: override INHIBIT_SYSROOT_STRIP for cross and native Hongxu Jia
2025-09-15 6:17 ` [PATCH 7/8] debug_build.inc: override MESON_BUILDTYPE for meson.bbclass Hongxu Jia
2025-09-15 6:17 ` [PATCH 8/8] debug_build.inc: override BUILD_MODE and BUILD_DIR " Hongxu Jia
2025-09-16 0:25 ` [OE-core] " Peter Kjellerstedt
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=20091.1757995157141119644@lists.openembedded.org \
--to=hongxu.jia@eng.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