[Mesa-dev] Can't run OpenGL ES demos
mattst88 at gmail.com
Fri Apr 15 12:33:47 PDT 2011
On Fri, Apr 15, 2011 at 2:39 PM, Chia-I Wu <olvaffe at gmail.com> wrote:
> On Sat, Apr 16, 2011 at 2:20 AM, Matt Turner <mattst88 at gmail.com> wrote:
>> I'm having trouble running any OpenGL ES programs from mesa-demos. It
>> seems to be identical to what was reported here
>> I'm using a Sandy Bridge system. Direct Rendering is working.
>> Mesa was configured with
>> ./configure --prefix=/usr --build=x86_64-pc-linux-gnu
>> --host=x86_64-pc-linux-gnu --mandir=/usr/share/man
>> --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
>> --localstatedir=/var/lib --libdir=/usr/lib64 --disable-option-checking
>> --with-driver=dri --disable-glut --without-demos --enable-xcb
>> --disable-debug --disable-glw --disable-motif --enable-glx-tls
>> --enable-asm --with-dri-drivers=swrast,i965 --enable-gles1
>> --enable-gles2 --enable-egl --disable-openvg --disable-gallium
>> --disable-gallium-egl --with-egl-platforms=wayland,drm,x11
>> Don't know if it's helpful, but here's the output from eglinfo:
> eglinfo reports only OpenGL support. It could be that a wrong DRI
> driver (/usr/lib64/dri/i965_dri.so) was loaded. It the path is
> correct, can you set a breakpoint at intelInitScreen2 and see which
> bits of api_mask are set?
Indeed, there's the problem. api_mask is 1. Looking at the build logs,
I see that the -DFEATURE_ES defines weren't being added to the command
to compile intel_screen.c (and other driver files) but were used in
the compilation of other mesa core files.
I removed --enabled-shared-dricore from my configure line (I didn't
even mention it earlier because I didn't think it was important) and
now -DFEATURE_ES1=1 -DFEATURE_ES2=1 are used to compile the intel
driver. So, looks like a regression due to the shared-dricore work.
More information about the mesa-dev