Zengtudor/glew-cmake
1
0
Fork 0
mirror of https://github.com/Perlmint/glew-cmake.git synced 2024-11-11 09:33:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

*** empty log message ***

Browse Source 
git-svn-id: https://glew.svn.sourceforge.net/svnroot/glew/trunk/glew@121 783a27ee-832a-0410-bc00-9f386506c6dd
This commit is contained in:
ikits 2003-09-15 16:04:41 +00:00
parent cd64fd9607
commit ffcdedcdd9
2 changed files with 46 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
auto/src/glew_post.html
View File

@ -4,7 +4,7 @@
<table border="0" cellspacing="0" cellpadding="0" width="100%"> <table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr> <tr>
<td align="right"> <td align="right">
<i>Last update: 08-11-03</i></td> <i>Last update: 09-15-03</i></td>
</tr> </tr>
</table> </table>
</td> </td>

77
doc/README.html
View File

@ -119,30 +119,35 @@ There are two ways to build your project with GLEW.
<p> <p>
The simpler but less flexible way is to include <tt>glew.h</tt> and The simpler but less flexible way is to include <tt>glew.h</tt> and
<tt>glew.c</tt> into your project and on Windows define the <tt>glew.c</tt> into your project and define the <tt>GLEW_STATIC</tt>
<tt>GLEW_STATIC</tt> preprocessor constant for the static library or preprocessor constant for the static library or executable you are
executable you are building together with GLEW. You also need to building together with GLEW (Windows only). You also need to replace
replace <tt>&lt;GL/gl.h&gt;</tt> and <tt>&lt;GL/glu.h&gt;</tt> with <tt>&lt;GL/gl.h&gt;</tt> and <tt>&lt;GL/glu.h&gt;</tt> with
<tt>&lt;glew.h&gt;</tt> and set the appropriate include flag <tt>&lt;glew.h&gt;</tt> in your code and set the appropriate include
(<tt>-I</tt>) to tell the compiler where to look for it. For example: flag (<tt>-I</tt>) to tell the compiler where to look for it. For
example:
<blockquote><pre>#include &lt;glew.h&gt; <blockquote><pre>#include &lt;glew.h&gt;
#include &lt;GL/glut.h&gt; #include &lt;GL/glut.h&gt;
&lt;gl, glu, and glut functionality is available here&gt; &lt;gl, glu, and glut functionality is available here&gt;
</pre></blockquote> </pre></blockquote>
Note that if you are using GLEW together with GLUT, you have to Depending on where you put <tt>glew.h</tt> you may also need to change
include <tt>glew.h</tt> first. In addition, <tt>glew.h</tt> includes the include directives in <tt>glew.c</tt>. Note that if you are using
<tt>glu.h</tt>, so you don't need to include it separately. GLEW together with GLUT, you have to include <tt>glew.h</tt> first.
In addition, <tt>glew.h</tt> includes <tt>glu.h</tt>, so you don't
need to include it separately.
<p> <p>
On Windows you can also add the supplied project file On Windows you also have the option of adding the supplied project
<tt>glew_static.dsp</tt> to your workspace (solution) and compile it together file <tt>glew_static.dsp</tt> to your workspace (solution) and compile
with your other projects. In this case you need to change the it together with your other projects. In this case you need to change
<tt>GLEW_BUILD</tt> preprocessor constant to <tt>GLEW_STATIC</tt>, the <tt>GLEW_BUILD</tt> preprocessor constant to <tt>GLEW_STATIC</tt>,
otherwise you get build errors. <b>Note that GLEW does not use the C otherwise you get build errors. <b>Note that GLEW does not use the C
runtime library, so it does not matter which version (single-threaded, runtime library, so it does not matter which version (single-threaded,
multi-threaded or multi-threaded DLL) it is linked with</b>. 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.</b>
<p> <p>
@ -260,6 +265,7 @@ if (GLEW_OK != err)
fprintf(stderr, "Error: %s\n", glewGetErrorString(err)); fprintf(stderr, "Error: %s\n", glewGetErrorString(err));
... ...
} }
fprintf(stdout, "Status: Using GLEW %s\n", glewGetString(GLEW_VERSION));
</pre></blockquote> </pre></blockquote>
<p> <p>
@ -352,7 +358,7 @@ else
<p> <p>
GLEW provides two command line tools: one for creating a list of 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. entry points.
<p> <p>
@ -361,11 +367,11 @@ entry points.
<p> <p>
<tt>wglinfo</tt> is the Windows version of <tt>glxinfo</tt>. By <tt>wglinfo</tt> is the Windows version of <tt>glxinfo</tt>. By
default it creates a file called <tt>wglinfo.txt</tt> that contains default it creates a file called <tt>wglinfo.txt</tt> that contains a
a list of available OpenGL, WGL, and GLU extensions list of available OpenGL, WGL, and GLU extensions as well as a table
as well as a table of visuals aka. pixelformats. Pbuffer and multiple output of visuals aka. pixel formats. Pbuffer and multiple output capable
capable visuals are also included. The format of the table is visuals are also included. The format of the table is described <a
described <a href="wglinfo.txt">here</a>. For additional usage information, type href="wglinfo.txt">here</a>. For additional usage information, type
<tt>wglinfo -h</tt>. <tt>wglinfo -h</tt>.
<p> <p>
@ -374,9 +380,10 @@ described <a href="wglinfo.txt">here</a>. For additional usage information, type
<p> <p>
<tt>glewinfo</tt> allows you to verify the entry points for the <tt>glewinfo</tt> allows you to verify the entry points for the
extensions supported on your platform. It uses GLEW to find out which extensions extensions supported on your platform. It uses GLEW to find out which
and entry points are available. On Windows it reports the results to a text file extensions and entry points are available. On Windows it reports the
called <tt>glewinfo.txt</tt>, on Linux and IRIX it prints them to <tt>stdout</tt>. results to a text file called <tt>glewinfo.txt</tt>, on Linux and IRIX
it prints them to <tt>stdout</tt>.
<p> <p>
</td> </td>
@ -394,13 +401,13 @@ called <tt>glewinfo.txt</tt>, on Linux and IRIX it prints them to <tt>stdout</tt
Starting from release 1.1.0, the source code and parts of the Starting from release 1.1.0, the source code and parts of the
documentation are automatically generated from the extension documentation are automatically generated from the extension
specifications via a two-step process. In the first step, specifications via a two-step process. In the first step,
specification files from the registry are parsed and skeleton specification files from the OpenGL registry are parsed and skeleton
descriptors are created for each extension. These descriptors contain descriptors are created for each extension. These descriptors contain
all necessary information for creating the source code and all necessary information for creating the source code and
documentation in a simple and compact format, including the the documentation in a simple and compact format, including the name of
extension name, url, tokens, function declarations, typedefs and the extension, url, tokens, function declarations, typedefs and struct
struct definitions. In the second step, the header files as well as definitions. In the second step, the header files as well as the
the library and glewinfo source are generated from the descriptor library and glewinfo source are generated from the descriptor
files. The code generation scripts are located in the <tt>auto</tt> files. The code generation scripts are located in the <tt>auto</tt>
subdirectory. subdirectory.
@ -441,10 +448,10 @@ effect token and function pointer definitions.
GLEW requires GLX 1.2 to assure compatibility with GLUT. In addition, GLEW requires GLX 1.2 to assure compatibility with GLUT. In addition,
the SGI GLX video extensions are currently not supported. the SGI GLX video extensions are currently not supported.
<p> <p>
Note that according to some <a Note that according to <a
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/opengl/ntopnglr_6yer.asp">WGL documentation</a> you have to initialize the entry points href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/opengl/ntopnglr_6yer.asp">WGL documentation</a> you have to initialize the entry points
for every rendering context you create. GLEW ignores this for every rendering context you create. <b>GLEW ignores this
requirement, and does not define per context entry points. This means requirement, and does not define per-context entry points.</b> This means
that you need to call <tt>glewInit()</tt> only once in your program, that you need to call <tt>glewInit()</tt> only once in your program,
or more precisely, once per process. We have not noticed any problems or more precisely, once per process. We have not noticed any problems
so far from ignoring the specification. so far from ignoring the specification.
@ -492,6 +499,12 @@ generation scripts are released under the <a href="gpl.txt">GPL</a>.
<p> <p>
<ul class="none"> <ul class="none">
<li><b>1.1.2</b> [09-15-03]
<ul>
<li> Removed dependency on WGL_{ARB,EXT}_extensions_string
<li> Added glewGetString for querying GLEW version string
</ul>
<p>
<li><b>1.1.1</b> [08-11-03] <li><b>1.1.1</b> [08-11-03]
<ul> <ul>
<li> Added GLX_NV_float_buffer <li> Added GLX_NV_float_buffer
@ -570,7 +583,7 @@ generation scripts are released under the <a href="gpl.txt">GPL</a>.
<table border="0" cellspacing="0" cellpadding="0" width="100%"> <table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr> <tr>
<td align="right"> <td align="right">
<i>Last update: 08-11-03</i></td> <i>Last update: 09-15-03</i></td>
</tr> </tr>
</table> </table>
</td> </td>