From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] package/waffle: new package
Date: Tue, 18 Sep 2018 09:31:10 +0200 [thread overview]
Message-ID: <20180918093110.4dd932d1@windsurf> (raw)
In-Reply-To: <207cc677-6028-81a1-f338-22711d152bc1@smile.fr>
Hello,
On Mon, 17 Sep 2018 21:59:46 +0200, Romain Naour wrote:
> > config BR2_PACKAGE_WAFFLE_SUPPORTS_GBM
> > bool
> > # mesa3d is for now the only GBM provider, and it is enabled
> > # together with its EGL support
> > default y if BR2_PACKAGE_HAS_LIBEGL && BR2_PACKAGE_MESA3D_OPENGL_EGL && BR2_PACKAGE_HAS_UDEV
>
> I believe this comment will be not correct as soon as the libgbm virtual package
> will be merged.
Indeed, but I wrote this example code for the current master, i.e
without the libgbm virtual package merged. Once it is merged, it is not
only the comment that will be wrong, but also the
BR2_PACKAGE_MESA3D_OPENGL_EGL dependency that will have to be replaced
by BR2_PACKAGE_HAS_LIBGBM.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-18 7:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 16:21 [Buildroot] [PATCH v2 1/3] package/python-numpy: add host variant for piglit Romain Naour
2018-02-11 16:21 ` [Buildroot] [PATCH v2 2/3] package/waffle: new package Romain Naour
2018-03-30 13:54 ` Valentin Korenblit
2018-09-16 21:30 ` Thomas Petazzoni
2018-09-17 19:59 ` Romain Naour
2018-09-18 7:31 ` Thomas Petazzoni [this message]
2018-02-11 16:21 ` [Buildroot] [PATCH v2 3/3] package/piglit: " Romain Naour
2018-03-30 14:01 ` Valentin Korenblit
2018-04-01 17:07 ` Romain Naour
2018-09-16 21:38 ` Thomas Petazzoni
2018-09-17 20:10 ` Romain Naour
2018-09-18 7:51 ` Thomas Petazzoni
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=20180918093110.4dd932d1@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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