Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Meta-OpenEmbedded Mailing listing
	<openembedded-devel@lists.openembedded.org>
Subject: Error message about multiple EGL / GLES providers
Date: Mon, 20 May 2013 20:18:16 +0200	[thread overview]
Message-ID: <519A68E8.9080503@pseudoterminal.org> (raw)

Hello,

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

I set the PREFERRED_PROVIDERS in the machine config file like this:

PREFERRED_PROVIDER_virtual/egl_cubox ?= "marvell-libgfx"
PREFERRED_PROVIDER_virtual/libgles1_cubox ?= "marvell-libgfx"
PREFERRED_PROVIDER_virtual/libgles2_cubox ?= "marvell-libgfx"

which is the way pretty much all layers seem to do it.

I remember a discussion about this, with the outcome that these errors 
are inevitable in danny, and that dylan has
special features in place to deal with the collisions between platform 
EGL/GLES drivers and mesa. However, I cannot
find such a feature.

Does anybody know more?

cheers



             reply	other threads:[~2013-05-20 18:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 18:18 Carlos Rafael Giani [this message]
2013-05-21  9:45 ` Error message about multiple EGL / GLES providers Burton, Ross
2013-05-21 10:08   ` Carlos Rafael Giani
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=519A68E8.9080503@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