>From a build of master (41eab95b3bc29a4fe6fd08b7f1f80cef5bdc097f) [1]:
$ lib nm libOSMesa.so | grep "EGL"
0000000000064254 t _mesa_EGLImageTargetRenderbufferStorageOES
00000000000b30c0 t _mesa_EGLImageTargetTexture2DOES
U glEGLImageTargetRenderbufferStorageOES
U glEGLImageTargetTexture2DOES
000000000029bb70 T mglEGLImageTargetRenderbufferStorageOES
000000000029bb90 T mglEGLImageTargetTexture2DOES
this prevents using libOSMesa, since one gets link errors about the
symbol.
Similar output for libMesaGL.
I shouldn't get any EGL when using --disable-egl, right?. Maybe this
is just the luxury edition...
Side note: libGLU is linked against libOSMesa, so there are issues
using that in a mangled setting as well. Seems strange that GLU would
need OSMesa symbols, but I'll admit to not keeping up with devel
lately.
-tom
[1]
./configure \
CFLAGS="-g -DUSE_MGL_NAMESPACE" \
CXXFLAGS="-g -DUSE_MGL_NAMESPACE" \
--prefix=${PF} \
--without-demos \
--with-driver=osmesa \
--disable-gallium \
--disable-egl \
--with-max-width=16384 \
--with-max-height=16384 \
--enable-glx-tls || exit 1
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
