Re,
As said in another mail, I agree for glext.h but not for GL.h. Or if we go that way, why not ship a 'valid' set of gl.h / glext.h / glxext.h that are known to work instead of redoing all the constants ?
Curiously, why glext and not gl? I'd be more for shipping all 3 if required or merging them all into one wine header. Could we not just be causing ourselves the same problem further down the line otherwise?
I not approve to merge all gl headers into one HUGE header. I only want to have its the minimalist header where we only define what we need.
For example, we know that Raphael has a configuration where his tree builds... Well, let him ship his .hs in Wine :-)
Perhaps they are copyright nvidia? :-)
Yes, but i think they redistribuable. (they are here: http://cvs1.nvidia.com/inc/GL/) Else we can always use last mesa headers.
Jason
Raphael
Theyre proprietary and only have GL 1.1 & 1.2 version.
Perhaps they are copyright nvidia? :-)
Yes, but i think they redistribuable. (they are here: http://cvs1.nvidia.com/inc/GL/) Else we can always use last mesa headers.
Jason
Raphael
===== Sylvain Petreolle (spetreolle at users dot sourceforge dot net) ICQ #170597259 No more War !
"What if tomorrow the War could be over ?" Morpheus, in "Reloaded".
For the Law of Oil and Fire, Im an European that lives in France. For all my Brothers and friends, Im a human living on Earth.
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com