From: Trevor Woerner <twoerner@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] systemd-systemctl-native: disable meson's auto-features
Date: Fri, 25 Apr 2025 12:42:46 -0400 [thread overview]
Message-ID: <20250425164246.GA554@localhost> (raw)
In-Reply-To: <CANNYZj-qO0jngKgSDGoUSsCsFvafJJgq_Q611HCAZcf-oVTH2Q@mail.gmail.com>
On Wed 2025-04-23 @ 05:00:42 PM, Alexander Kanavin wrote:
> This sounds like something that should be in meson.bbclass, rather
> than one specific recipe?
As an experiment I moved the --auto-features=disabled flag to the
meson.bbclass. Unsurprisingly when doing a world build of oe-core a bunch of
additional recipes fail. Surprisingly the list is not as long as I would have
thought:
gconf (+native)
efivar
libfm
consolekit
cairo (+native)
pulseaudio
I'm working through the list to discover which features are being
auto-detected rather than explicitly set. For each feature I'm adding a
PACKAGECONFIG, then enabling it by default.
If I can get through the above list successfully then I'll have a v2 to send.
Realistically I should do the same exercise with meta-oe before sending a v2.
> Alex
>
> On Wed, 23 Apr 2025 at 15:52, Trevor Woerner via
> lists.openembedded.org <twoerner=gmail.com@lists.openembedded.org>
> wrote:
> >
> > Disable meson's ability to analyze the entire host's system to determine which
> > features to enable. Which features are enabled should be limited to the
> > features that are explicitly enabled, not simply discovered.
> >
> > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> > ---
> > meta/recipes-core/systemd/systemd-systemctl-native_257.5.bb | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-core/systemd/systemd-systemctl-native_257.5.bb b/meta/recipes-core/systemd/systemd-systemctl-native_257.5.bb
> > index 041a040a2654..591a1747d63a 100644
> > --- a/meta/recipes-core/systemd/systemd-systemctl-native_257.5.bb
> > +++ b/meta/recipes-core/systemd/systemd-systemctl-native_257.5.bb
> > @@ -8,7 +8,7 @@ inherit pkgconfig meson native
> >
> > MESON_TARGET = "systemctl:executable"
> > MESON_INSTALL_TAGS = "systemctl"
> > -EXTRA_OEMESON += "-Dlink-systemctl-shared=false"
> > +EXTRA_OEMESON += "-Dlink-systemctl-shared=false --auto-features=disabled"
> >
> > # Systemctl is supposed to operate on target, but the target sysroot is not
> > # determined at run-time, but rather set during configure
> > --
> > 2.44.0.501.g19981daefd7c
> >
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#215309): https://lists.openembedded.org/g/openembedded-core/message/215309
> > Mute This Topic: https://lists.openembedded.org/mt/112414248/1686489
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
prev parent reply other threads:[~2025-04-25 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 13:52 [PATCH] systemd-systemctl-native: disable meson's auto-features Trevor Woerner
2025-04-23 15:00 ` [OE-core] " Alexander Kanavin
2025-04-25 16:42 ` Trevor Woerner [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=20250425164246.GA554@localhost \
--to=twoerner@gmail.com \
--cc=alex.kanavin@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