Created attachment 107558 [details]
Add DEF files for GLES1/GLES2
GLES1 and GLES2 are missing DEF files for their respective DLLs.
I assume you copied the list of functions from the ABI-check scripts. Those lists contain more than what you actually want to export. See the FIXME comments at the top. For instance, glMultiDrawArraysEXT shouldn't be exported.
I just took the existing decorated exports (via 'dumpbin /exports') and stripped the prefix/suffixes.
Created attachment 107563 [details] [review]
Add DEF files for GLES1/GLES2, take 2
This time around I took the exports directly from GLES/gl.h and GLES2/gl2.h.
Created attachment 115005 [details] [review]
Add DEF files for GLES1/GLES2, take 3
Threw in the GLES3 symbols too.
Does this really work on Windows?
I thought that now that we removed st/egl from Mesa, EGL would be totally broken. I was actually planing to stop building EGL on Windows.
My recommendation to use GLES1/GLES2 on Windows would be to use the wgl_ext_create_context_es2_profile with the opengl32.dll we provide.
Still working as of cb154bb22116910c462f7a83f4401bd01e15c34d
(In reply to Charles Huber from comment #6)
> Still working as of cb154bb22116910c462f7a83f4401bd01e15c34d
That's 10.4 branch.
I think this has been broken apart in master:
There were two EGL implementations: a DRI Linux-specific one, and a cross-platform one, but nobody was interested in maintaining the later one.
I wonder if you truly need EGL on Windows, or WGL_EXT_create_context_es_profile could meet your needs. Even if you truly need EGL on Windows, I'm afraid that unless somebody is willing to maintain it, it's not going to come back to life...
In short, the patch you proposed only makes sense in the 10.4 branch.