I’m trying to create OpenGL bindings for flat assembler (on windows).
Therefore I need to parse the C headers, or at least I have choosen to do so. Well I have written a simple python script that does just that and it works quite well for the gl3.h and wglext.h files.
However I can’t find the download location for wgl.h and glx.h, maybe you can give me a link?
Maybe it is even possible to create bindings without them? (I wish to target OpenGL 3+ exclusivly.)
But how would I create a 3+ context without a dummy context?
Can I use LoadLibrary and GetProcAddress to get access to wglCreateContextAttribsARB and if it is not available assume GL3+ is not supported?
Another Problem I have is understanding how OpenGL works when multiple different graphic cards are installed. Are there multiple OpenGL32.dll’s? I exspect not, but how are different context on different graphic cards handled, especially if both cards have different features.
For example many 3+ tutorials first create a dummy context to get access to the wgl functions and then create a new context. But is it in any way guaranteed that the new context is handled by the same card?
Do you know any good and up-to-date tutorials that explain manual extension handling on windows? It seems GLEW is used almost exclusivly, but thats not possible with fasm.
Thanks in advance.