On 1/25/06, IOhannes m zmoelnig zmoelnig@iem.at wrote:
well, glew will "define" every possible extension (e.g. "GL_APPLE_texture_range" will be defined), since this is a preprocessor thing and would just be an annoyance for a runtime checker.
the clause
<snip> #ifdef GL_APPLE_texture_range #endif </snip> has to be replaced by <snap> if (GLEW_APPLE_texture_range){ } </snap>
if this is what you meant by having "to clean up some code based on platform assumptions in order to make it work", then i'd answer "YES".
The other option is to add in those platform and vendor specific defines by adding a __APPLE__ to the preprocessor check.
Either way is about the same amount of work, but moving to GLEW also introduces a dependency on another lib for GEM. Hopefully, they keep it up to date on all three platforms.
The other assumptions are any places where __APPLE__ really means PowerPC and so on.
btw, welcome to the joys of compiling things on platforms where the headers do not exactly match the installed libraries....
It's really a piece of work that Windows OS.