OpenGL version about caelina HOT 9 CLOSED

Please remember that OES is considered a set of subsets of desktop GL. Supporting desktop GL functionality inherently means supporting GL ES functionality. Therefore, switching to a purely OES specification would be considered a downgrade. That being said, the plan is to implement as much of GL 1.1 as possible then support for newer specifications will be added, as well as adding OES headers and functions.

from caelina.

Ok, guess I will wait before contributing then, since most of the stuff I worked on is only available after 1.3 or 1.4. Thanks for the clarification

from caelina.

You are welcome to contribute anything not specified in GL 1.1 as long as it adheres to OpenGL's specification and the conventions currently in use in the implementation. Note that any functions added must check if g_state is null, check if it isn't allowed in glBegin/glEnd blocks, and if it can be cached into a display list, it must add itself to the currently compiling list and be called by executeList. Most importantly, it mustn't break other functions.

from caelina.

What about the missing defines? What value should those take and where should those be added?

from caelina.

Some defines are missing because Mesa3D's gl.h depends on Khronos' glext.h. Download the official glext.h and check if the defines are in there first. Currently, the glext.h being used just defines glScissorMode, which should be moved out into a different header since it isn't an official extension.

from caelina.

I've decided to include Khronos' glext.h, and any "unregistered extensions" such as the PICA200's inverted scissor mode will be added to GL/ctr.h

from caelina.

I'm starting to think we should implement our own glext.h, according to https://www.opengl.org/registry : /#headers <GL/glext.h> - OpenGL 1.2 and above compatibility profile and extension interfaces.

Most of what I saw in the Khronos header would be vendor specific anyway.

from caelina.

Please see the implementor's guide. Khronos specifies using their glext.h and any of the implementor's extensions that aren't registered must be placed into the implementor's own headers.

from caelina.

Oh, right. Guess this answers all my questions then ! Thanks.

from caelina.