From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/5] mesa: don't build empty libgles3-mesa in GLVND case
Date: Tue, 20 May 2025 20:45:25 +0300 [thread overview]
Message-ID: <20250520174529.1173460-1-dmitry.baryshkov@oss.qualcomm.com> (raw)
If GLVND is enabled, there is no libgles2-mesa package to depend on
libgles3-mesa. Stop building unused empty package in this case.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
---
meta/recipes-graphics/mesa/mesa.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/mesa/mesa.inc b/meta/recipes-graphics/mesa/mesa.inc
index 288027bbb996..89ae71595991 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -247,7 +247,7 @@ RDEPENDS:libgles3-mesa-dev += "libgles2-mesa-dev"
# GLES2 and GLES3 implementations are packaged in a single library in libgles2-mesa.
# Add a dependency so the GLES3 dev package is associated with its implementation.
RDEPENDS:libgles2-mesa += "libgles3-mesa"
-ALLOW_EMPTY:libgles3-mesa = "1"
+ALLOW_EMPTY:libgles3-mesa = "${@bb.utils.contains('PACKAGECONFIG', 'glvnd', '', '1', d)}"
RDEPENDS:libopencl-mesa += "${@bb.utils.contains('PACKAGECONFIG', 'opencl', 'libclc spirv-tools spirv-llvm-translator', '', d)}"
--
2.39.5
next reply other threads:[~2025-05-20 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 17:45 Dmitry Baryshkov [this message]
2025-05-20 17:45 ` [PATCH 2/5] mesa: drop the libopencl-mesa-dev package Dmitry Baryshkov
2025-05-20 17:45 ` [PATCH 3/5] mesa: don't add extra tags to the libopencl-mesa package Dmitry Baryshkov
2025-05-20 17:45 ` [PATCH 4/5] mesa: don't set RCONFLICTS / PROVIDES if glvnd is enabled Dmitry Baryshkov
2025-05-20 17:45 ` [PATCH 5/5] mesa: sort out PROVIDES for the glvnd case Dmitry Baryshkov
2025-05-21 9:03 ` [OE-core] [PATCH 1/5] mesa: don't build empty libgles3-mesa in GLVND case Böszörményi Zoltán
2025-05-21 13:51 ` Dmitry Baryshkov
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=20250520174529.1173460-1-dmitry.baryshkov@oss.qualcomm.com \
--to=dmitry.baryshkov@oss.qualcomm.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