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:02:32 -0400	[thread overview]
Message-ID: <20160426140232.GC31113@denix.org> (raw)
In-Reply-To: <CAJTo0LaE9PTEG6zsasGc_H6ngw4Oq=BFZBTZQ4ynszdtUTV3QQ@mail.gmail.com>

On Tue, Apr 26, 2016 at 12:36:10PM +0100, Burton, Ross wrote:
> On 22 April 2016 at 01:27, Christopher Larson <clarson@kergoth.com> wrote:
> 
> > 1. Change weston recipe in oe-core to depend on libgbm instead of
> >> virtual/mesa
> >> assuming that it is provided by mesa recipe and it works for other
> >> platforms.
> >>
> >
> > I'd say this, either libgbm or virtual/libgbm.
> >
> 
> We used virtual/mesa to mean "the Mesa APIs and so on" so libgbm is covered
> by this.  Of course at the time there was only one implementation in mesa.
> Now that there are genuine alternative reimplementations of libgdm then I
> agree that a virtual/libgbm is a good move, and replacing all of the
> virtual/mesa instances that are actually just for libgdm.

Thanks, Ross, that makes sense.

-- 
Denys


  reply	other threads:[~2016-04-26 14:02 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
2016-04-26 11:36   ` Burton, Ross
2016-04-26 14:02     ` Denys Dmytriyenko [this message]
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=20160426140232.GC31113@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