From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/2] add an SDK_FEATURES lever
Date: Thu, 6 Aug 2026 20:17:42 -0400 [thread overview]
Message-ID: <20260807001744.3874352-1-twoerner@gmail.com> (raw)
SDK contents are close to all-or-nothing today. The one lever that
exists, SDK_TOOLCHAIN_LANGS, has the right shape but only ever covered
languages.
Add SDK_FEATURES, in the spirit of DISTRO_FEATURES and IMAGE_FEATURES,
and fold SDK_TOOLCHAIN_LANGS into it. BB_RENAMED_VARIABLES keeps the old
name working.
Every SDK_FEATURES test resolves inside TOOLCHAIN_HOST_TASK and
TOOLCHAIN_TARGET_TASK, which are packagegroup lists read at populate_sdk
time. Nothing in a compiler's configure ever sees SDK_FEATURES, so
changing it rebuilds no toolchain and two SDKs with different features
share everything underneath. That property is the point of the design and
the rest of this work depends on it.
This changes no existing SDK: SDK_FEATURES defaults to empty, and
BB_RENAMED_VARIABLES maps SDK_TOOLCHAIN_LANGS onto it so configurations
still using the old name keep working.
Changes in v2:
- autobuilder.conf keeps += rather than switching to :append
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Trevor Woerner (2):
bitbake.conf: add an SDK_FEATURES lever
sdk: fold SDK_TOOLCHAIN_LANGS into SDK_FEATURES
meta/classes-recipe/populate_sdk_base.bbclass | 21 +++++++++----------
meta/conf/bitbake.conf | 2 ++
meta/conf/documentation.conf | 1 +
.../yocto-autobuilder/autobuilder.conf | 2 +-
.../packagegroups/packagegroup-core-sdk.bb | 2 +-
5 files changed, 15 insertions(+), 13 deletions(-)
--
2.50.0.173.g8b6f19ccfc3a
next reply other threads:[~2026-08-07 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 0:17 Trevor Woerner [this message]
2026-08-07 0:17 ` [PATCH v2 1/2] bitbake.conf: add an SDK_FEATURES lever Trevor Woerner
2026-08-07 0:17 ` [PATCH v2 2/2] sdk: fold SDK_TOOLCHAIN_LANGS into SDK_FEATURES Trevor Woerner
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=20260807001744.3874352-1-twoerner@gmail.com \
--to=twoerner@gmail.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