From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Supporting GLES-only implementations
Date: Sat, 03 Mar 2012 18:26:22 +0100 [thread overview]
Message-ID: <4F52543E.3020705@gentoo.org> (raw)
I'm trying to get better support for efika and possibly other similar
systems like pandaboard.
I already started to hack eselect-opengl and mesa to keep libGLES*,
libOpenVG and libEGL in the switchable dir and it seems to work properly.
Now I'd like to make ALL the GL/ GLES/ KHR/ and such headers switchable
as well.
One of the last items is discussing about what to do with
implementations that do not provide OpenGL.
I'd introduce a separate virtual for gles2, gles1 and openvg and make so
eselect-opengl does not complain if libGL is missing.
Anybody has interest and/or better ideas?
lu
PS: I'd consider GL implementations monolithic so you cannot mix and
match them at least for now.
--
Luca Barbato
Gentoo/linux
http://dev.gentoo.org/~lu_zero
next reply other threads:[~2012-03-03 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 17:26 Luca Barbato [this message]
2012-03-04 13:40 ` [gentoo-dev] Supporting GLES-only implementations Luca Barbato
-- strict thread matches above, loose matches on Subject: below --
2012-03-25 1:14 Luca Barbato
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=4F52543E.3020705@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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