From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/opengl: ensure consistency between the various providers
Date: Fri, 17 Feb 2017 09:34:38 +0100 [thread overview]
Message-ID: <20684119.X7ZmMtA3r5@sagittae> (raw)
In-Reply-To: <681a6c09-1976-193c-a738-ff948ff86567@mind.be>
Hello Yann,
On Thursday 16 February 2017 18:46:10 CET Arnout Vandecappelle wrote:
>
> On 14-02-17 22:13, Yann E. MORIN wrote:
> > Some GL providers will provide libegl and libgles, but not libgl, while
> > other will provide libgl but not libegl not libgles. This can be the
> > case with:
> > - mesa3d -> libgl
> > - rpi-userland -> libegl and libgles
Unfortunately, as far as I remember, this kind of configuration is
necessary to build xdriver_xf86-video-imx-viv. Mesa is necessary to
build GLX support but, EGL/GLes have to be provided by imx-gpu-viv.
However, maybe your idea is correct and xdriver_xf86-video-imx-viv should be
reworked (but it is not a trivial work).
> The commit message is missing an explanation of why this is bad... Something
> like "Such a situation leads to conflicting headers and libraries when building
> a package that uses both libgl and libegl."
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2017-02-17 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 21:13 [Buildroot] [PATCH] package/opengl: ensure consistency between the various providers Yann E. MORIN
2017-02-16 17:46 ` Arnout Vandecappelle
2017-02-16 17:56 ` Yann E. MORIN
2017-02-17 7:56 ` Arnout Vandecappelle
2017-02-17 22:19 ` Yann E. MORIN
2017-02-17 8:34 ` Jérôme Pouiller [this message]
2017-02-17 10:04 ` Thomas Petazzoni
2017-02-17 17:06 ` Jérôme Pouiller
2017-03-26 21:48 ` 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=20684119.X7ZmMtA3r5@sagittae \
--to=jezz@sysmic.org \
--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