forcing inclusion of glext.h and the use of glext prototypes causes programs (like glaxium) to fail building because they use the opposite code path in glext.h (when GL_GLEXT_PROTOTYPES is not defined)
Would this occure still IF we removed the checks for GL_GLEXT_PROTOTYPES and just had everything defined from both code paths? Basically is the failure a duplicate definition or something else?
glaxium defines a bunch of prototypes that the headers are forced to define normally glaxium would define the prototypes and follow the code path opposite of what is currently forced either way, the headers shouldnt be screwed up like this becuase who knows what other applications we broke (things that arent in portage; perhaps projects that people have made themselves)
Reversed the patch, now glext.h is only included, GL_GLEXT_PROTOTYPES is not defined...
mmm just checked cvs and the define is still there ? nvidia-glx/files/1.0.6111/NVIDIA_glx-1.0.6111-glheader.patch
Vapier : yes the patch is still there, but all it does is now include GL/glext.h Or is the point that you want glext.h not included?
Well i didnt commit before (but we know that), this was fixed up a while back now Closing. glext.h should be included from gl.h
