Hi JS, On Wed, Oct 6, 2010 at 6:15 PM, Jean-Sébastien Guay <[email protected]> wrote: > Seeing as no one has needed to change the calling convention of GL (as > defined in GL_APIENTRY or APIENTRY) before to my knowledge, I think it > should be fine. Once you move those things to a namespace I think it'll be > even more redundant. > > Try it and we'll see. Thanks,
I've added the following to mipmap.c and tess.h: // simply define GLAPIENTRY as nothing so that we can keep function signatures the same as declaration. #define GLAPIENTRY Things still compile on my system just fine. Could you do an svn update and let me know if things progress any further at your end. On the glTexImage3D front it looks like mipmap.c has it's own local gluTexImage3D implementation for getting the extension. The code looks to me like it should work under Windows, on the OSG side we have our own extension methods so we might be able to leverage these, but this itself is fraught with integration issues as we build things around the idea of a ContextID mapping to extension objects for each context. It looks to me that the GLU code in Mesa may well not be robust in the presence of multiple contexts... If we can't get it working right away then just #if'ing out the glTexImage3D codes might be the sensible thing to do. We can come back to this later. I will now have a look at the casting issues. Robert. _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
