On Mon, May 10, 2010 at 11:17 AM, tom fogal <tfo...@alumni.unh.edu> wrote: > Dan Nicholson <dbn.li...@gmail.com> writes: >> On Mon, May 10, 2010 at 10:08 AM, Kevin H. Hobbs <hob...@ohiou.edu> wrote: > >> > All I really want is Mesa with OSMesa from the development >> > repository as the "reference" library for my VTK and ParaView >> > nightly test builds. >> >> ./configure --with-driver=xlib ? That will link libOSMesa to libGL, >> but that's what configs/linux-x86-64 is already doing (I think). If >> that's not working for you, please let me know. I tried to make this >> work correctly in the past, but personally use the dri drivers. > > We build like that already to satisfy VTK; I didn't realize OSMesa > would appear in that library as well, so we did a second build for > OSMesa. This would simplify things significantly. I will give it a > try later today.
The configure flag is --enable-gl-osmesa. The difference with --with-driver=osmesa is that you link to libGL instead of libmesa.a and friends, so you couldn't distribute libOSMesa.so standalone. See CORE_MESA in src/mesa/drivers/osmesa/Makefile. > In some sense, it would still be nice to be able to work with a library > that was only OSMesa. I imagine the additional code needed for libGL > isn't all that much, though. I think the osmesa code is the same, it's just a matter of symbol resolution. The build machinery doesn't currently support gl + standalone osmesa in one pass, though. -- Dan _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
