From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: tom.hochstein@oss.nxp.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3 5/5] mesa: Fix missing GLES3 headers in SDK sysroot
Date: Mon, 23 Dec 2024 11:28:52 +0000 [thread overview]
Message-ID: <2bd2615ee9d8ba12c0dcc0888057140debfbce4a.camel@linuxfoundation.org> (raw)
In-Reply-To: <20241222162234.2411262-5-tom.hochstein@oss.nxp.com>
On Sun, 2024-12-22 at 10:22 -0600, Tom Hochstein via lists.openembedded.org wrote:
> Building weston with core-image-weston SDK fails:
> ```
> ../libweston/renderer-gl/gl-shader-config-color-transformation.c:29:10: fatal error: GLES3/gl3.h: No such file or directory
> 29 | #include <GLES3/gl3.h>
> | ^~~~~~~~~~~~~
> ```
>
> Both GLES2 and GLES3 implementations are contained in libGLESv2.so.2,
> which is packaged in libgles2-mesa. However, the headers are split
> between libgles2-mesa-dev and libgles3-mesa-dev, which is why the
> GLES3 headers end up missing in the SDK sysroot.
>
> Add a dependency so the GLES3 headers are properly associated with
> the GLES3 implementation.
>
> Signed-off-by: Tom Hochstein <tom.hochstein@oss.nxp.com>
> ---
> meta/recipes-graphics/mesa/mesa.inc | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-graphics/mesa/mesa.inc b/meta/recipes-graphics/mesa/mesa.inc
> index 9fdf496e8b..84490158f1 100644
> --- a/meta/recipes-graphics/mesa/mesa.inc
> +++ b/meta/recipes-graphics/mesa/mesa.inc
> @@ -233,6 +233,10 @@ DEV_PKG_DEPENDENCY = ""
> # development package of libgles3.
> 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-dev += "libgles3-mesa-dev"
> +
> RDEPENDS:libopencl-mesa += "${@bb.utils.contains('PACKAGECONFIG', 'opencl', 'libclc spirv-tools', '', d)}"
This doesn't quite make sense to me. The line above that RDEPENDS is
adding a dependency in the opposite direction and will effectively make
one package uninstallable without the other.
The question is does the libgles2-mesa-dev package need the libgles3-
mesa-dev package? If not, this is not the right way to solve the
problem you're seeing.
Cheers,
Richard
next prev parent reply other threads:[~2024-12-23 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 16:22 [PATCH v3 1/5] pkgconfig: Add pkg-config-native to SDK Tom Hochstein
2024-12-22 16:22 ` [PATCH v3 2/5] wayland-protocols: Remove inoperative packaging override Tom Hochstein
2024-12-22 16:22 ` [PATCH v3 3/5] weston: Fix wayland-protocols dependency Tom Hochstein
2024-12-22 16:22 ` [PATCH v3 4/5] weston: Disable unused tests build Tom Hochstein
2024-12-22 16:22 ` [PATCH v3 5/5] mesa: Fix missing GLES3 headers in SDK sysroot Tom Hochstein
2024-12-23 11:28 ` Richard Purdie [this message]
2024-12-23 14:43 ` [OE-core] " Tom Hochstein
[not found] ` <18138C56105EEBAA.17446@lists.openembedded.org>
2024-12-22 16:24 ` Tom Hochstein
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=2bd2615ee9d8ba12c0dcc0888057140debfbce4a.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=tom.hochstein@oss.nxp.com \
/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.