Re: [Mesa3d-users] gl header file handling

[Brian P. <bri...@tu...>]

Ulrich von Zadow wrote:
> Hi,
> 
> we've got problems with different gl headers here - not all extensions 
> are defined in the headers on all plattforms etc. Of course, this is a 
> feature, not a bug, since vendor-specific extensions won't necessarily 
> be defined in other vendor's header files. Nonetheless, when you're 
> trying to distribute stuff to be compiled on user's machines (i.e. open 
> source sw), this is a hassle.
> 
> Besides using glXGetProcAddressARB and siblings where possible, I can 
> see two ways of handling this:
> 
> a) Including gl headers (found somewhere) with our source code that at 
> define
>    the stuff needed.
> b) Use the system gl headers and define needed extensions manually in an
>    application-specific header using #ifdef magic to avoid duplicate
>    definitions.
> 
> What are other people doing? Is this just a hassle that can't be avoided?

If you feel you can't rely on the pre-installed headers, I'd probably 
include a copy of the glext.h header file with my software.

glext.h is maintained by SGI and pretty much kept up to date with the 
latest OpenGL extensions.

http://oss.sgi.com/projects/ogl-sample/registry/

-Brian