Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Remove gl2x backed legacy methods from PGL #3674
When requesting GL2ES1 interface we used to get GL2/GL3bc/GL4bc implementation on desktop, which could be cast to GL2. After transition to GL2ES2 we are getting only GLES2 on mobile and core implementations (GL3/GL4) on desktop, which means that we can't get GL2 anymore (diagram).
I am not an expert on OpenGL interfaces or JOGL, but I believe I am getting a GL2 from the open source vc4 Mesa driver (on the Raspberry Pi), when I request a GL2ES2 (or GL2ES1).
Not sure if this plays any role in your considerations above, but just thought I mention it.
@gohai Try to run something with
Anyway, we are using GL2ES2 so we don't have to worry about this kind of stuff. I think it's time to get rid of the legacy stuff. Thoughts @codeanticode?
Yes, those calls were working on the Mesa driver with vc4 - it was only the (GLES2 only) binary driver that doesn't do those. Mesa implements the entire desktop GL stack for this hardware, but I think GL2 is as far as this (tiling) chip will ever go.. just saying that there might be some hardware that does GL2 but not GL3, as far as I understand.
This is the JOGL debug output for this configuration:
X11GraphicsDevice[type .x11, connection :0.0]: Natives GL4bc false GL4 false GLES3 false GL3bc false GL3 false GL2 true [2.1 (Compat profile, arb, compat[ES2], FBO, hardware)] GLES2 false GLES1 false Count 1 / 8 Common GL4ES3 false GL2GL3 true GL2ES2 true GL2ES1 true Mappings GL2ES2 GLProfile[GL2ES2/GL2.hw] GL2ES1 GLProfile[GL2ES1/GL2.hw] GL2 GLProfile[GL2/GL2.hw] GL2GL3 GLProfile[GL2GL3/GL2.hw] default GLProfile[GL2/GL2.hw] Count 4 / 12
changed the title from
Remove gl2x from PJOGL and throw warnings from affected methods
Remove gl2x backed legacy methods from PJOGL
Aug 21, 2015
We decided to keep GL2 and cascade through it for functions like
You will still be able to get GL2 through PGL and call them if you so desire, but it does not make sense to keep them in PGL API, because nearly none of our users on desktop are going to be able to use them anyway.