On Thu, 2009-01-22 at 13:15 +0000, José Fonseca wrote:
> Hi,
> 
> Mesa and Gallium3D include a big number of test and sample OpenGL apps.
> A good portion depends on Glut so it could be built on many platforms.
> Unfortunately, several samples which demonstrate recent OpenGL
> functionality call extensions entry points directly, which is not
> guaranteed to work on all platforms. GLEW library perfectly fills this
> gap, providing a uniform compatibility layer, and therefore allowing to
> build these sample apps with very little changes.
> 
> To make it easy to build the samples I plan to integrate the GLEW source
> code directly into Mesa:
> - include/GL/glew.h
> - include/GL/glxew.h
> - include/GL/wglew.h

Since we're not intending to be the install-source of GLEW on people's
system, I think the GLEW header files should go in src/glew/include.
The Makefiles in progs/* can just add -I$(topdir)/src/glew/include to
CFLAGS.

> - src/glew/LICENSE.txt
> - src/glew/glew.c
> - src/glew/glewinfo.c
> - src/glew/visualinfo.c
> 
> This is just the barely needed to build the samples (no code
> autogeneration harness or documentation). I don't expect we will need to
> update the glew code, but if we do, we would send the patches upstream.
> 
> Let me know if there's any issue with this.

Attachment: signature.asc
Description: This is a digitally signed message part

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to