From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v3 0/6] wic: ship its tools, and add an SDK_FEATURES lever
Date: Fri, 17 Jul 2026 09:34:15 -0400 [thread overview]
Message-ID: <20260717133421.3510970-1-twoerner@gmail.com> (raw)
wic shells out to a range of host-side tools but does not declare them,
so wherever it is installed as a package (rather than run from the
bitbake do_image_wic task, which has the wic-tools native sysroot on
PATH) it works only by chance depending on what the host has installed.
Patch 1 fixes that directly: wic gains RDEPENDS on the tools it runs, so
they are installed alongside it in every variant that packages it.
The rest of the series turns "what optional tools go into the SDK" into
an explicit, self-documenting choice. It introduces SDK_FEATURES, a list
in the same spirit as DISTRO_FEATURES / MACHINE_FEATURES / IMAGE_FEATURES:
a developer reads the setting and knows exactly what their SDK contains.
- patch 2 adds SDK_FEATURES and gates wic on the "wic" feature (off by
default);
- patch 3 moves the existing (unconditional, arch-gated) qemu addition
behind a "qemu" feature, on by default so nothing regresses;
- patch 4 adds an opt-in "sbom" feature (SPDX + SBOM/CVE tooling);
- patch 5 moves the cross-canadian gdb behind a "gdb" feature, on by
default; binutils and gcc stay unconditional since a cross-compiler
is intrinsic to an SDK;
- patch 6 adds an opt-in "lldb" feature for developers who prefer it.
The default SDK_FEATURES is "gdb qemu", so an unmodified configuration
produces the same SDK as before. The intent is to present the full range
of knobs and let review settle which belong on by default; the split
across separate patches is deliberate so each can be debated on its own.
SDK_FEATURES is a plain list, so downstream layers can define their own
features (for example a cgdb feature in meta-openembedded) the same way.
changes in v3:
- replace the SDK_INCLUDE_WIC yes/no knob with the general SDK_FEATURES
lever, and use it for qemu, sbom, gdb and lldb as well as wic
- the v2 "buildtools-extended-tarball: drop wic helper tools" patch was
merged already and is dropped from the series
changes in v2:
- dropped the wic-tools.inc refactor; folded the tool list into the wic
recipe
- reworked the buildtools-extended-tarball change into a plain removal
- gated wic in the SDK behind a knob instead of adding it unconditionally
Trevor Woerner (6):
wic: add runtime dependencies on the tools it invokes
nativesdk-packagegroup-sdk-host: add wic via a new SDK_FEATURES lever
nativesdk-packagegroup-sdk-host: gate qemu behind SDK_FEATURES
nativesdk-packagegroup-sdk-host: add an sbom SDK feature
packagegroup-cross-canadian: gate gdb behind SDK_FEATURES
nativesdk-packagegroup-sdk-host: add an lldb SDK feature
meta/conf/bitbake.conf | 2 +-
meta/conf/documentation.conf | 1 +
.../nativesdk-packagegroup-sdk-host.bb | 5 +++-
.../packagegroup-cross-canadian.bb | 2 +-
meta/recipes-support/wic/wic_0.3.1.bb | 23 +++++++++++++++++++
5 files changed, 30 insertions(+), 3 deletions(-)
--
2.50.0.173.g8b6f19ccfc3a
next reply other threads:[~2026-07-17 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 13:34 Trevor Woerner [this message]
2026-07-17 13:34 ` [PATCH v3 1/6] wic: add runtime dependencies on the tools it invokes Trevor Woerner
2026-07-17 13:34 ` [PATCH v3 2/6] nativesdk-packagegroup-sdk-host: add wic via a new SDK_FEATURES lever Trevor Woerner
2026-07-17 13:34 ` [PATCH v3 3/6] nativesdk-packagegroup-sdk-host: gate qemu behind SDK_FEATURES Trevor Woerner
2026-07-17 13:34 ` [PATCH v3 4/6] nativesdk-packagegroup-sdk-host: add an sbom SDK feature Trevor Woerner
2026-07-17 13:34 ` [PATCH v3 5/6] packagegroup-cross-canadian: gate gdb behind SDK_FEATURES Trevor Woerner
2026-07-17 13:34 ` [PATCH v3 6/6] nativesdk-packagegroup-sdk-host: add an lldb SDK feature 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=20260717133421.3510970-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