The OpenGL Extension Wrangler Library
| ||||||||||||
|
The goal of the OpenGL Extension Wrangler Library (GLEW) is to assist C/C++ OpenGL developers with two tedious tasks: initializing and using extensions and writing portable applications. GLEW provides an efficient run-time mechanism to determine whether a certain extension is supported by the driver or not. OpenGL core and extension functionality is exposed via a single header file. GLEW currently supports SGI systems and PCs with commodity graphics cards on three operating systems: Windows, Linux, and IRIX.
|
||||||||||||
|
Source and precompiled binaries are available at the project website.
|
||||||||||||
|
GLEW currently supports the following extensions: Useful links about OpenGL extensions:
|
||||||||||||
|
There are two ways to build your project with GLEW. Including the source files / project file The simpler but less flexible way is to include glew.h and glew.c into your project and on Windows define the GLEW_STATIC preprocessor constant for the static library or executable you are building together with GLEW. You also need to replace <GL/gl.h> and <GL/glu.h> with <glew.h> and set the appropriate include flag (-I) to tell the compiler where to look for it. For example: Note that if you are using GLEW together with GLUT, you have to include glew.h first. In addition, glew.h includes glu.h, so you don't need to include it separately.#include <glew.h> #include <GL/glut.h> <gl, glu, and glut functionality is available here> On Windows you can also add the supplied project file glew_static.dsp to your workspace (solution) and compile it together with your other projects. In this case you need to change the GLEW_BUILD preprocessor constant to GLEW_STATIC, otherwise you get build errors. Note that GLEW does not use the C runtime library, so it does not matter which version (single-threaded, multi-threaded or multi-threaded DLL) it is linked with. Using GLEW as a shared library Alternatively, you can use the provided project files / makefile to build a separate shared library you can link your projects with later. In this case the best practice is to install glew.h, glew32.lib, and glew32.dll / libGLEW.so to where the OpenGL equivalents gl.h, opengl32.lib, and opengl32.dll / libGL.so are located. Note that you need administrative privileges to do this. If you do not have administrator access and your system administrator will not do it for you, you can install GLEW into your own lib and include subdirectories and tell the compiler where to find it. Then you can just replace <GL/gl.h> with <GL/glew.h> in your program: or:#include <GL/glew.h> #include <GL/glut.h> <gl, glu, and glut functionality is available here> #include <GL/glew.h> <gl and glu functionality is available here> Don't forget to link your project with glew32.lib, glu32.lib, and opengl32.lib on Windows and libGLEW.so, libGLU.so, and libGL.so on Linux and IRIX (-lGLEW -lGLU -lGL). It is important to keep in mind that glew.h includes neither windows.h nor gl.h. Also, GLEW will warn you by issuing a preprocessor error in case you have included gl.h, glext.h, or glATI.h before glew.h.
|
||||||||||||
|
To install the shared library version of GLEW you need to copy the headers and libraries into their destination directories. On Windows this boils down to copying (no, we will not write a Windows installer for you).
where {VC Root} is your Visual C++ directory, typically C:/Program Files/Microsoft Visual Studio/VC98 for Visual Studio 6.0 or C:/Program Files/Microsoft Visual Studio/Vc7/PlatformSDK for Visual Studio .NET. On Linux and IRIX, typing "make install" will attempt to install GLEW into /usr/include/GL and /usr/lib. You can customize the installation target via the GLEW_DEST environment variable if you do not have write access to these directories.
|
||||||||||||
|
Initializing GLEW First you need to create a valid OpenGL rendering context and call glewInit() to initialize the extension entry points. If glewInit() returns GLEW_OK, the initialization succeeded and you can use the available extensions as well as core OpenGL functionality. For example: Querying the available OpenGL extensions Starting from GLEW 1.1.0, you can find out if a particular extension is available on your platform by querying globally defined variables of the form GLEW_{extension_name}: You can also check for core OpenGL functionality. For example, to see if OpenGL 1.3 is supported: For extensions glewGetExtension provides a slower alternative: Experimental drivers GLEW works by querying the supported extensions from the graphics driver. Experimental drivers, however, might not report every available extension through the standard mechanism, in which case GLEW will report it unsupported. To circumvent this situation, the glewExperimental global switch can be turned on by setting it to GL_TRUE before calling glewInit(). This makes sure that all extensions with valid entry points will be exposed. Platform specific extensions Platform specific extensions are separated into two header files: wglew.h and glxew.h, which define the available WGL and GLX extensions. To determine if a certain extension is supported, query WGLEW_{extension name} or GLXEW_{extension_name}. For example: | ||||||||||||
|
GLEW provides two command line tools: one for creating a list of available extensions and visuals; and another for verification of extension entry points. wglinfo: extensions and visuals on Windows wglinfo is the Windows version of glxinfo. By default it creates a file called wglinfo.txt that contains a list of available OpenGL, WGL, and GLU extensions as well as a table of visuals aka. pixelformats. Pbuffer and multiple output capable visuals are also included. The format of the table is described here. For additional usage information, type wglinfo -h. glewinfo: extension verification utility glewinfo allows you to verify the entry points for the extensions supported on your platform. It uses GLEW to find out which extensions and entry points are available. On Windows it reports the results to a text file called glewinfo.txt, on Linux and IRIX it prints them to stdout.
|
||||||||||||
|
Starting from release 1.1.0, the source code and parts of the documentation are automatically generated from the extension specifications via a two-step process. In the first step, specification files from the registry are parsed and skeleton descriptors are created for each extension. These descriptors contain all necessary information for creating the source code and documentation in a simple and compact format, including the the extension name, url, tokens, function declarations, typedefs and struct definitions. In the second step, the header files as well as the library and glewinfo source are generated from the descriptor files. The code generation scripts are located in the auto subdirectory.
|
||||||||||||
|
To avoid name clashes when linking with libraries that include the same symbol, extension entry points are declared in a separate namespace (release 1.1.0 and up). This is achieved by aliasing OpenGL function names to their GLEW equivalents. For instance, glFancyFunction is simply an alias to glewFancyFunction. Note that the separate namespace doesn't effect token and function pointer definitions.
|
||||||||||||
|
GLEW requires GLX 1.2 to assure compatibility with GLUT. In addition, the SGI GLX video extensions are currently not supported. Note that according to some WGL documentation you have to initialize the entry points for every rendering context you create. GLEW ignores this requirement, and does not define per context entry points. This means that you need to call glewInit() only once in your program, or more precisely, once per process. We have not noticed any problems so far from ignoring the specification.
|
||||||||||||
|
GLEW was developed by Milan Ikits and Marcelo Magallon. They also perform occasional maintainance to make sure that GLEW stays in mint condition. Aaron Lefohn, Joe Kniss, and Chris Wyman were the first users and also assisted with the design and debugging process. The acronym GLEW originates from Aaron Lefohn. Pasi Kärkkäinen identified and fixed several problems with GLX and SDL. The RPM packages are maintained by Karol Pietrzak. Nate Robins created the wglinfo utility, to which modifications were added by Michael Wimmer.
GLEW is originally derived from the EXTGL project by Lev Povalahev. The source code is licensed under the modified BSD license, the SGI Free Software License B, and the GLX Public License. The automatic code generation scripts are released under the GPL. |
||||||||||||
|
|
||||||||||||
|
