From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Ash Charles <ashcharles@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: virtual/mesa, virtual/libgl provided by multiple packages
Date: Fri, 27 Jun 2014 09:22:19 +0100 [thread overview]
Message-ID: <53AD29BB.2060901@dynamicdevices.co.uk> (raw)
In-Reply-To: <CAK8F28=CotBOqPE30quGM_k5aQG7sYnw8kPmNtn6i+6DtCNwfQ@mail.gmail.com>
On 26/06/2014 22:51, Ash Charles wrote:
> Hi Alex,
> On Fri, Jun 13, 2014 at 1:49 PM, Alex J Lennon
> <ajlennon@dynamicdevices.co.uk> wrote:
>> I think these two lines in cogl-1.0.inc are causing mesa to be pulled in
>> incorrectly, but I'm not sure what ERDEPENDS does...
>>
>> # Extra RDEPENDS for PACKAGECONFIG
>> # This has to be explictly listed, because cogl dlopens the backends
>> ERDEPENDS_GL = "libgl"
>> ERDEPENDS_GLES2 = "libgles2"
> I'm seeing the same issue. I'm guessing that 'virtual/*' is not a
> valid target for an RDEPEND. It looks like your libgles2 provider
> should RPROVIDE libgles2. The receipe for SGX (graphics core)
> libraries, for example, contains lines like this:
> RREPLACES_${PN} = "libegl libgles1 libgles2"
> RPROVIDES_${PN} = "libegl libgles1 libgles2"
> RCONFLICTS_${PN} = "libegl libgles1 libgles2"
>
> Mesa does something similar (with some extra debian renaming that I
> didn't understand) in an anonymous python function in mesa.inc.
>
> --Ash
fwiw. I also ran into a problem with needing libglapi which seems to be
provided by mesa.
I am wondering if there's a need for a mesa-glapi similar to mesa-gl to
eliminate the need for mesa-proper
Regards, Alex
prev parent reply other threads:[~2014-06-27 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 22:44 virtual/mesa, virtual/libgl provided by multiple packages Chris Morgan
2014-05-28 20:31 ` Khem Raj
2014-06-13 19:45 ` Alex J Lennon
2014-06-13 20:27 ` Chris Morgan
2014-06-13 20:49 ` Alex J Lennon
2014-06-26 21:51 ` Ash Charles
2014-06-27 8:22 ` Alex J Lennon [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=53AD29BB.2060901@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=ashcharles@gmail.com \
--cc=yocto@yoctoproject.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.