[Mesa-dev] [Bug 30172] GL_EXT_framebuffer_blit function required

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Sep 16 12:08:29 PDT 2010


--- Comment #17 from Brian Paul <brianp at vmware.com> 2010-09-16 12:08:29 PDT ---
(In reply to comment #16)
> Perhaps a sensible resolution is to only export those symbols if a binary-only
> application is found requiring them, which works on another GL implementation.

I agree that if there's an existing application that fails out of the box w/
Mesa but not NVIDIA or AMD for this reason, we should then export the function
too.  There's no sense in punishing end users like that.

> Although I'm personally for preventive action, following the "liberal" part of
> "be conservative in what you do, be liberal in what you accept from others".
> And yes, that does encourage applications to be broken, but the fault for that
> lies in AMD and nVidia.
> At a more fundamental level, it lies in whoever reinvented the wheel by adding
> glXGetProcAddress instead of just using ELF weak symbols (or dlsym if you
> somehow insist on querying symbols by string).

I was involved in developing glXGetProcAddress.  Back then, I'm not sure that
dlsym() was widely available on all the flavors of Unix having OpenGL.  There
was also the possibility of using X/GLX on non-Unix systems.

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the mesa-dev mailing list