From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Error message about multiple EGL / GLES providers
Date: Tue, 21 May 2013 12:08:56 +0200 [thread overview]
Message-ID: <519B47B8.7090002@pseudoterminal.org> (raw)
In-Reply-To: <CAJTo0LaYF2oHHH=Pgz1kqbLyM1D-Q4AVg5O0ChCwU_wwD_J8+w@mail.gmail.com>
On 2013-05-21 11:45, Burton, Ross wrote:
> On 20 May 2013 19:18, Carlos Rafael Giani <dv@pseudoterminal.org> wrote:
>> I am currently adapting the cubox layer for dylan, and get these errors:
>>
>> ERROR: Multiple .bb files are due to be built which each provide
>> virtual/libgles1
>> ERROR: Multiple .bb files are due to be built which each provide
>> virtual/libgles2
>> ERROR: Multiple .bb files are due to be built which each provide virtual/egl
> What are the bb files that are being build? I'm guessing mesa and
> marvell-libgfx, but can you confirm this? If you use depexp you can
> find out what's pulling in mesa, but it's generally mesa-demos. This
> depends on virtual/libgl that you're not providing, so it will pull in
> Mesa.
>
> If you don't have any support for "big" GL then the easiest fix is to
> take the recent patches to mesa-demos in master that let you turn off
> GL using PACKAGECONFIG options.
>
> Ross
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
The collision is indeed between marvell-libgfx and mesa, I just
verified. My case is actually quite common with embedded 3D hardware -
EGL, OpenGL ES 1.x,2.x and OpenVG are supported, but desktop OpenGL
isn't. I have seen this with nVidia Tegra, Vivante, PowerVR, and ARM
Mali hardware so far. It would be useful to instruct Mesa to turn off
its OpenGLES and EGL support, leaving Mesa only for GLX+Desktop OpenGL
(software-rendered), if anybody really needs it. As an alternative, as
you suggest, I could simply turn off desktop OpenGL, but I have the
feeling that this would be better off as a user decision that can be
configured in the local.conf file. What do you think?
next prev parent reply other threads:[~2013-05-21 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 18:18 Error message about multiple EGL / GLES providers Carlos Rafael Giani
2013-05-21 9:45 ` Burton, Ross
2013-05-21 10:08 ` Carlos Rafael Giani [this message]
2013-05-21 10:51 ` Paul Barker
2013-05-21 15:22 ` Burton, Ross
2013-05-21 16:47 ` Otavio Salvador
2013-05-21 16:57 ` Carlos Rafael Giani
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=519B47B8.7090002@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=openembedded-devel@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