diff --git a/auto/src/glew_post.html b/auto/src/glew_post.html index 99bdf6a..411d5d6 100644 --- a/auto/src/glew_post.html +++ b/auto/src/glew_post.html @@ -4,7 +4,7 @@ +Last update: 09-15-03
-Last update: 08-11-03
diff --git a/doc/README.html b/doc/README.html index 77d02da..bc89ec1 100644 --- a/doc/README.html +++ b/doc/README.html @@ -119,30 +119,35 @@ There are two ways to build your project with GLEW.

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: +glew.c into your project and define the GLEW_STATIC +preprocessor constant for the static library or executable you are +building together with GLEW (Windows only). You also need to replace +<GL/gl.h> and <GL/glu.h> with +<glew.h> in your code and set the appropriate include +flag (-I) to tell the compiler where to look for it. For +example: 

#include <glew.h>
 #include <GL/glut.h>
 <gl, glu, and glut functionality is available here>
-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. +Depending on where you put glew.h you may also need to change +the include directives in glew.c. 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.

-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, +On Windows you also have the option of adding 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. +multi-threaded or multi-threaded DLL) it is linked with (without +debugging information). It is, however, a good idea to compile all +your projects including GLEW with the same C runtime settings.

@@ -260,6 +265,7 @@ if (GLEW_OK != err) fprintf(stderr, "Error: %s\n", glewGetErrorString(err)); ... } +fprintf(stdout, "Status: Using GLEW %s\n", glewGetString(GLEW_VERSION));

@@ -352,7 +358,7 @@ else

GLEW provides two command line tools: one for creating a list of -available extensions and visuals; and another for verification of extension +available extensions and visuals; and another for verifying extension entry points.

@@ -361,11 +367,11 @@ entry points.

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 +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. pixel formats. Pbuffer and multiple output capable +visuals are also included. The format of the table is described here. For additional usage information, type wglinfo -h.

@@ -374,9 +380,10 @@ described here. For additional usage information, type

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. +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.

@@ -394,13 +401,13 @@ called glewinfo.txt, on Linux and IRIX it prints them to stdoutauto subdirectory. @@ -441,10 +448,10 @@ 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 +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. @@ -492,6 +499,12 @@ generation scripts are released under the GPL.