On Tue, Nov 15, 2011 at 9:08 PM, Matthew Cattell <mcatt...@spamarrest.com> wrote: > Brian Paul <brianp <at> vmware.com> writes: > >> >> On 03/10/2011 08:30 PM, tom fogal wrote: >> > Kenneth Graunke<kenneth <at> whitecape.org> writes: >> >> On Thursday, March 10, 2011 01:17:04 PM Alexander Neundorf wrote: >> >>> While at it (sorry for newbie questions), do I need gallium (maybe >> >>> swrast) when I want only osmesa rendering into a software buffer ? >> >> >> >> I don't think OSMesa requires Gallium, but I've never used it. >> > >> > Kenneth's correct. We build OSMesa all the time without gallium. In >> > this case OSMesa uses the swrast driver/backend/whatnot. The 'xlib' >> > driver also uses this backend. >> > >> > I believe there is a way to build both of these on top of softpipe -- >> > the software/reference gallium implementation -- but my project hasn't >> > jumped on that boat yet. Someday. >> >> OSMesa doesn't work with gallium yet. I'd like to do that sometime >> though. llvmpipe would be much faster than swrast in many cases. >> >> -Brian >> > > > Hi, > > I've been trying to build mesa with the following combination: > osmesa > llvm > egl > gles2 > (with and without --with-drivers=fbdev,wayland) For fb only, GLES2, swrast EGL, you may try
$ ./configure --disable-opengl --enable-gles2 --enable-gallium-egl \ --with-gallium-drivers=swrast --with-egl-platforms=fbdev If you also need OSMesa, this may work $ ./configure --disable-dri --disable-glx --enable-gles2 --enable-osmesa --enable-gallium-egl \ --with-gallium-drivers=swrast --with-egl-platforms=fbdev I do not really try to build. Some of the options may only available on the master branch. > I am puzzled about the terminology but when I got my build to succeed, using a > sha1 from 14th July 2011, I tried testing it and found that eglInitialize was > failing. This was apparently because it couldn't find the display. I am using > and X-less environment and want to render directly to fb0 or to some shared > memory, hence the inclusion of osmesa. > > Am I on the right track here? The combinations of autoconf options seem to > change a lot and I can't find much in the way of documentation to see which > combinations and options are valid and correct for the particular sha1 I'm > using. > > Can you point me in the right direction? > > Best Regards, > > Matthew Cattell > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/mesa-dev > -- o...@lunarg.com _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev