Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

egl_and_glx_different_pointers test is insane #165

Closed
nwnk opened this issue Apr 9, 2018 · 1 comment
Closed

egl_and_glx_different_pointers test is insane #165

nwnk opened this issue Apr 9, 2018 · 1 comment

Comments

@nwnk
Copy link
Collaborator

nwnk commented Apr 9, 2018

/**
 * @file egl_and_glx_different_pointers.c
 *
 * Tests that epoxy correctly handles an EGL and GLX implementation
 * that return different function pointers between the two.
 *
 * This is the case for EGL and GLX on nvidia binary drivers
 * currently, but is also the case if someone has nvidia binary GLX
 * installed but still has Mesa (software) EGL installed.  This seems
 * common enough that we should make sure things work.
 */

I don't know if this is still the case for the NVIDIA drivers, but it's certainly no longer true for glvnd systems. Even in the described configuration, epoxy would likely not work in such a scenario. Whichever provider (either GLX or EGL) you had current when you first resolved glVertex3f would be the only one it ever dispatched to.

@anholt
Copy link
Owner

anholt commented Apr 9, 2018

Yeah, I thought it was pretty crazy, but people were also complaining about it being broken at the time. "No, use glvnd" seems like a fairly reasonable response at this point.

@ebassi ebassi closed this as completed in 5fa7bf6 Apr 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants