Re: intel and gallium swrast
Andrea Giammarchi <[email protected]>
| Newsgroups | gmane.comp.video.mesa3d.user |
|---|---|
| Message-ID | <CADA77mhrE+oKNe8GDbz7DVZP2xodEtcCVyXOzZuPU30NDSrhCw@mail.gmail.com> |
actually, simply dropping gallium drivers like this --with-gallium-drivers= did the trick ... question would be now: is this defaulting to dri/drm whatever it is or I still need somehow the gallium software compatibility fallback? Thanks again On Thu, Jul 3, 2014 at 9:46 PM, Andrea Giammarchi < [email protected]> wrote: > Hello there, first post here so let's start with a big Thank You! for mesa > > I've been building mesa master for Wayland for weeks now without problems > and here how I do this for an Intel based netbook > > WLD=/usr > > ./autogen.sh --prefix=$WLD --libdir=$WLD/lib \ > --enable-gles2 \ > --enable-gbm \ > --enable-shared-glapi \ > --with-egl-platforms=wayland,drm \ > --disable-gallium-egl \ > --with-gallium-drivers=swrast \ > --disable-glx --disable-xa \ > --with-dri-drivers=i915,i965,swrast > > Everything has always been OK but now the autogen shows me a new entry > beside the gallium, called pipe-loader, and both > `src/gallium/state_tracker/dri/sw` and `src/gallium/state_tracker/dri/drm` > has files that simply points to `../common/filename.c` or .h like > dri_context.c or dri_screen and these files, being just empty files with a > path specified as first line, fails. > > I wonder if there's something I'm missing from latest or as configuration, > since copying over whatever is in common inside these two folders did not > work at all. > > Any hint would be appreciated, thank again and Best Regards > > > > > > _______________________________________________ mesa-users mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-users