Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Christopher Larson <clarson@kergoth.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: mesa, libgbm and weston
Date: Tue, 26 Apr 2016 10:05:50 -0400	[thread overview]
Message-ID: <20160426140550.GD31113@denix.org> (raw)
In-Reply-To: <CAJTo0LZCgoyt8GyvbkhvsK4_Q8v5MgU3O+0FFXGaajyyiDS0Zg@mail.gmail.com>

On Tue, Apr 26, 2016 at 12:59:05PM +0100, Burton, Ross wrote:
> On 25 April 2016 at 17:50, Denys Dmytriyenko <denis@denix.org> wrote:
> 
> > One other thing I was thinking is how to avoid conflict between separate
> > libgbm and the one provided by mesa-gl. As mesa-gl may be useful for
> > providing
> > SW rendering for OpenGL, while leaving OpenGLES to a separate provider,
> > like
> > SGX. Unfortunately, mesa-gl also provides libgbm - would PACKAGECONFIG to
> > use
> > a standalone external libgbm work and be acceptable here?
> >
> 
> I added a PACKAGECONFIG for libgbm to mesa.inc, enabled it for mesa and
> disabled it for mesa-gl, and mesa-gl still build fine but didn't ship a
> libgbm.
> 
> I've forgotten the details about all of this: does mesa-gl shipping libgbm
> make sense at all?  Or in the real world will BSPs either use mesa or their
> own GLES driver + their own libgbm + mesa-gl if required?

Hmm, that is a good question. Probably expecting a separate libgbm by default 
when using own GLES driver + mesa-gl does make sense. I wonder if anyone is 
using the one from mesa-gl with their own GLES, then we would need it 
configurable via PACKAGECONFIG...

-- 
Denys


  parent reply	other threads:[~2016-04-26 14:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22  0:05 mesa, libgbm and weston Denys Dmytriyenko
2016-04-22  0:27 ` Christopher Larson
2016-04-25 16:50   ` Denys Dmytriyenko
2016-04-26 11:59     ` Burton, Ross
2016-04-26 14:00       ` Burton, Ross
2016-04-26 14:27         ` Denys Dmytriyenko
2016-04-26 14:49           ` Otavio Salvador
2016-04-26 14:05       ` Denys Dmytriyenko [this message]
2016-04-26 11:36   ` Burton, Ross
2016-04-26 14:02     ` Denys Dmytriyenko
2016-04-26 19:06     ` Burton, Ross

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=20160426140550.GD31113@denix.org \
    --to=denis@denix.org \
    --cc=clarson@kergoth.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox