From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] OpenGL packaging/staging policy
Date: Tue, 23 Oct 2012 10:49:06 +0100 [thread overview]
Message-ID: <50866812.10408@r-finger.com> (raw)
In-Reply-To: <CAPj87rOZokkPT_a7kbaqmai2bWwV5xLL8oV2UNOfoxkARHfwCg@mail.gmail.com>
On 23/10/12 10:18, Daniel Stone wrote:
>> Regardless what is done with the packaging, allowing only mesa to stage
>> dev files will break things. GL headers are not interchangeable, even if
>> all the implementers are well behaved (which is a big if), the
>> *platform.h files are allowed to be implementation specific and so have
>> to be staged by the actual platform GL stack.
>
> Right, I do agree with you, but in the mixed-stack situation, which
> headers are we building against? :)
The GL / GLES / GLES2 / EGL headers are separate from each other, so in
theory if you have separate libgl, libles, libgles2, and libegl
packages, you could even stage them from four different sources. But for
the Cedar Trail scenario a separate big GL and a combined GLES/GLES2/EGL
package, plus a package for common libs. This might be of some use for
others (IIRC, the whole discussion about this was sparked after enabling
EGL in the mesa package), though it means building mesa multiple times.
Tomas
next prev parent reply other threads:[~2012-10-23 10:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 16:35 [RFC] OpenGL packaging/staging policy Burton, Ross
2012-10-22 17:19 ` Tomas Frydrych
2012-10-22 19:27 ` Burton, Ross
2012-10-22 20:25 ` Tomas Frydrych
2012-10-23 2:06 ` Daniel Stone
2012-10-23 8:37 ` Tomas Frydrych
2012-10-23 9:18 ` Daniel Stone
2012-10-23 9:49 ` Tomas Frydrych [this message]
2012-10-29 17:26 ` Burton, Ross
2012-10-29 17:26 ` [OE-core] " Burton, Ross
2012-10-29 18:27 ` Tomas Frydrych
2012-11-20 16:52 ` Burton, Ross
2012-11-20 16:52 ` [OE-core] " Burton, Ross
2012-10-22 17:32 ` [oe] " Phil Blundell
2012-10-22 17:38 ` Otavio Salvador
2012-10-22 19:26 ` Burton, Ross
2012-10-22 17:33 ` Otavio Salvador
2012-10-22 17:33 ` [OE-core] " Otavio Salvador
2012-10-22 19:25 ` Phil Blundell
2012-10-22 19:25 ` [OE-core] " Phil Blundell
2012-10-22 17:37 ` Mark Hatle
2012-10-22 19:29 ` 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=50866812.10408@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.