All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Hochstein <tom.hochstein@oss.nxp.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	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 08:43:54 -0600	[thread overview]
Message-ID: <a413da4e-dc93-484b-b90a-d6826a528efc@oss.nxp.com> (raw)
In-Reply-To: <2bd2615ee9d8ba12c0dcc0888057140debfbce4a.camel@linuxfoundation.org>

On 12/23/2024 5:28 AM, Richard Purdie wrote:
>>
>> +# 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.
> 

Does this work better, signifying that libgles2-mesa contains libgles3-
mesa?

+RDEPENDS:libgles2-mesa += "libgles3-mesa"
+ALLOW_EMPTY:libgles3-mesa = "1"

Tom




  reply	other threads:[~2024-12-23 14:44 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   ` [OE-core] " Richard Purdie
2024-12-23 14:43     ` Tom Hochstein [this message]
     [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=a413da4e-dc93-484b-b90a-d6826a528efc@oss.nxp.com \
    --to=tom.hochstein@oss.nxp.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.