From: <mingli.yu@eng.windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] gcr: add opengl to REQUIRED_DISTRO_FEATURES
Date: Fri, 23 Dec 2022 17:32:29 +0800 [thread overview]
Message-ID: <20221223093229.823322-1-mingli.yu@eng.windriver.com> (raw)
From: Mingli Yu <mingli.yu@windriver.com>
Fixes:
$ bitbake gcr
ERROR: Nothing PROVIDES 'gtk4' (but /build/layers/oe-core/meta/recipes-gnome/gcr/gcr_4.0.0.bb DEPENDS on or otherwise requires it)
gtk4 was skipped: missing required distro feature 'opengl' (not in DISTRO_FEATURES)
ERROR: Required build target 'gcr' has no buildable providers.
Missing or unbuildable dependency chain was: ['gcr', 'gtk4']
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
---
meta/recipes-gnome/gcr/gcr_4.0.0.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-gnome/gcr/gcr_4.0.0.bb b/meta/recipes-gnome/gcr/gcr_4.0.0.bb
index 264069ffd1..22edd386fc 100644
--- a/meta/recipes-gnome/gcr/gcr_4.0.0.bb
+++ b/meta/recipes-gnome/gcr/gcr_4.0.0.bb
@@ -20,6 +20,8 @@ GTKDOC_MESON_OPTION = "gtk_doc"
inherit gnomebase gtk-icon-cache gi-docgen features_check upstream-version-is-even vala gobject-introspection gettext mime mime-xdg
UPSTREAM_CHECK_REGEX = "gcr-(?P<pver>\d+\.(\d*[02468])+(\.\d+)+)\.tar.xz"
+REQUIRED_DISTRO_FEATURES = "${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'opengl', '', d)}"
+
SRC_URI += "file://0001-meson.build-correctly-handle-disabled-ssh_agent-opti.patch"
SRC_URI[archive.sha256sum] = "c45855924f0ee7bab43e2dd38bfafd2ac815c6e9864341c0161e171173dcec7c"
--
2.25.1
next reply other threads:[~2022-12-23 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 9:32 mingli.yu [this message]
2022-12-23 9:43 ` [OE-core] [PATCH] gcr: add opengl to REQUIRED_DISTRO_FEATURES Alexander Kanavin
2023-01-05 2:10 ` Yu, Mingli
2023-01-05 6:55 ` Alexander Kanavin
2023-01-06 9:11 ` Yu, Mingli
2023-01-06 9:19 ` Alexander Kanavin
2023-01-06 10:36 ` Richard Purdie
2023-01-06 10:47 ` Martin Jansa
2023-01-06 10:58 ` Alexander Kanavin
2023-01-06 11:10 ` Richard Purdie
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=20221223093229.823322-1-mingli.yu@eng.windriver.com \
--to=mingli.yu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.