Mark Kilgard wrote:
>
> Brian and oglbase,
>
> Even including <windows.h> with WIN32_LEAN_AND_MEAN defined
> creates a large amount of name space pollution.
>
> It is a tad involved, but GLUT goes through careful contortions
> to be able to include the <GL/gl.h> without including
> <windows.h>.
>
> Should a similar scheme be used for <GL/glext.h>?
>
> Ultimately, what'd I'd like is a <GL/gl.h> and <GL/glu.h>
> for Win32 that doesn't require including <windows.h>. It is
> not all that hard, though it is unlikely that Microsoft would
> distribute such a file. It might be nice though to have
> a <GL/gl.h> and <GL/glu.h> suitable for Win32 compilation
> that doesn't require <windows.h> namespace pollution.
I guess someone who knows the ins&outs of Windows programming
should see that gl.h and glext.h has the right code. I'm (happily)
clueless in that area.
-Brian
