From: Ross Burton <ross.burton@intel.com>
To: Ian Geiser <igeiser@devonit.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: OpenGL as a DISTRO_FEATURE
Date: Sun, 3 Feb 2013 19:04:18 +0000 [thread overview]
Message-ID: <50E181AF64EF4AF9835BF9FD769D9B93@intel.com> (raw)
In-Reply-To: <B57A220D1EE1644685BA9AD5C790D20526BE045F3A@SOUTHSIDE.devonintlgroup.com>
On Sunday, 3 February 2013 at 17:15, Ian Geiser wrote:
> Greetings, I maintain 3 different platforms with varying degrees of GL support. Would it make more sense to migrate the "opengl" distro feature to MACHINE_FEATURES? This way we could compensate for the platforms that use Mesa and the ones that use their custom implementations? Thoughts?
Even if there were machine features, a distro feature is still something you'd want.
There's been the idea of having fine-grained machine features for the aspects of OpenGL that the hardware supports (gl, gles, egl, etc). It's not as simple as it appears and causes a rather large number of packages to become machine-specific.
What would you use the machine features for? Conditionally compiling support for a particular variant of GL into packages that cannot be detected at runtime, or something else?
Ross
next prev parent reply other threads:[~2013-02-03 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 17:15 OpenGL as a DISTRO_FEATURE Ian Geiser
2013-02-03 19:04 ` Ross Burton [this message]
2013-02-03 19:45 ` Ian Geiser
2013-02-03 21:33 ` Marcin Juszkiewicz
2013-02-03 23:35 ` Ross Burton
2013-02-04 0:53 ` Ian Geiser
2013-02-05 20:58 ` Tomas Frydrych
2013-02-07 14:25 ` Andrei Gherzan
2013-02-04 0:53 ` Ian Geiser
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=50E181AF64EF4AF9835BF9FD769D9B93@intel.com \
--to=ross.burton@intel.com \
--cc=igeiser@devonit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox