On 03/04/2013 01:32 PM, Matt Turner wrote: > > Committed. Thanks! Before this change ( at least this is the most reasonable change from last night ) I would configure mesa with :
./autogen.sh \ --prefix=/home/kevin/mesa_nightly \ --enable-glx \ --with-dri-drivers=swrast \ --with-gallium-drivers=swrast \ --enable-osmesa and according to VTK's LoadOpenGLExtension test in fact I got : http://open.cdash.org/testDetails.php?test=179582680&build=2835185 GL_VENDOR: VMware, Inc. GL_VERSION: 2.1 Mesa 9.2-devel (git-b88f74d) GL_RENDERER: Gallium 0.4 on llvmpipe (LLVM 3.0, 128 bits) but today I get : http://open.cdash.org/testDetails.php?test=179722202&build=2836181 GL_VENDOR: Mesa Project GL_VERSION: 2.1 Mesa 9.2-devel (git-e21460b) GL_RENDERER: Software Rasterizer so now configure is giving me exactly what I asked for which is good :-) Unfortunately it isn't what I want :-( and the swrast driver gives me more vtk test errors than the llvmpipe driver :-( I have spare cycles on some machines I might be able to test VTK on all of the mesa software renderers and nouveau but for now how do I get the old behavior? "configure --help" gives me only an example with swrast. ./autogen.sh \ --prefix=/home/kevin/mesa_nightly \ --enable-glx \ --with-gallium-drivers=llvmpipe \ --enable-osmesa Fails: configure: error: Package requirements (libdrm_nouveau >= 2.4.33) were not met: On fedora it's : $ cat /usr/lib64/pkgconfig/libdrm_nouveau2.pc | grep Name Name: libdrm_nouveau2 ./autogen.sh \ --prefix=/home/kevin/mesa_nightly \ --enable-glx \ --with-dri-drivers= \ --with-gallium-drivers=llvmpipe \ --enable-osmesa Fails: configure: error: Unknown Gallium driver: llvmpipe
signature.asc
Description: OpenPGP digital signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
