Hi Nigel/All,

After going through the code I have found that significant work has been done for adding the OpenGL ES 2.0 support to glew lib.
However still few things are missing like adding the runtime entrypoint for OpenGL ES extension functions, adding support for EGL to glew.

However for sometime there has been no update. So I would like to extend the implementation further.
Kindly provide your feedback.



On 5 February 2011 13:33, Nigel Stewart <nstewart@nvidia.com> wrote:
Hi Shariq,

There was some previous discussion about ES and EGL:



In a nutshell I think we agree that GLEW ought to
support ES and EGL.  But nobody has stepped up to
do the work yet.  I havn't done a diff with the
openreng fork for a while, to be clear about that.
But it could be a useful starting point.

- Nigel

On 2/2/11 3:46 AM, Shariq Hasnain wrote:
Dear All,

I was thinking for extending the glew lib to support OpenGL ES and EGL similarly to that of OpenGL and WGL/GLX.
Since OpenGL ES is popularly used in embedded domain it will be a good idea to do so.
-It will provide run time determination of OpenGL ES/EGL extension supported in the target platform.
-This will also make the porting of OpenGL applications using glew to OpenGL ES easier as the GLEW related code need not be modified individually for each applications.

The idea is to have:
 - Run time check for OpenGL ES core/extension functions similar as existing OpenGL core/extension support in GLEW library.
 - Run time check for EGL core/extension functions similar as existing GLX/WGL support in GLEW library.
 - Since EGL is used for Graphics resource management in embedded, GLX and WGL support will not be provided.

Kindly provide your feedback.


This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.