Mangled or no, "glXGetProcAddressARB" exists in Mesa's libGL. From a
mangled install:
$ nm ~/sw/mesa-git/lib/libMesaGL.so.1 | grep -i glxgetprocad
000000000004d321 T glXGetProcAddressARB
000000000004d366 T mglXGetProcAddress
$ grep "glXGetProcAddress" ~/sw/mesa-git/include/GL/glx_mangle.h
#define glXGetProcAddress mglXGetProcAddress
$
Arguably, this is correct, since the Linux OpenGL ABI specifies that
this entry point *must* be defined. OTOH, this would prevent an
application from linking both /usr/lib/libGL.so && a custom-built
mangled Mesa GL, yes? Or rather, if an application developer called
"glXGetProcAddressARB", they might expect to call mangled Mesa but
instead call their /usr/lib's GPA-ARB.
This is unfortunately still relevant, because an app I work on cannot
rely on glXGPA existing; at least one user's OGL implementation only
has glXGPA-ARB (i.e. doesn't support 1.4).
The attached diff is one fix. Is it the correct one?
-tom
diff --git a/include/GL/glx_mangle.h b/include/GL/glx_mangle.h
index 4439a96..fa664a7 100644
--- a/include/GL/glx_mangle.h
+++ b/include/GL/glx_mangle.h
@@ -76,6 +76,7 @@
/* GLX 1.4 */
#define glXGetProcAddress mglXGetProcAddress
+#define glXGetProcAddressARB mglXGetProcAddressARB
#endif
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
