> if test -n "$with_gallium_drivers" -a "x$with_gallium_drivers" != xswrast;
> then
> if test "x$enable_xvmc" = xauto -a "x$have_xvmc_platform" = xyes; then
> PKG_CHECK_EXISTS([xvmc >= $XVMC_REQUIRED], [enable_xvmc=yes],
> [enable_xvmc=no])
> fi
> ...
> fi
>
> Thus auto-detection w
On Wed, 24 Apr 2019 at 13:09, Emil Velikov wrote:
>
> On Tue, 23 Apr 2019 at 23:10, Alyssa Ross wrote:
> >
> > > Off the top of my head - none of the VL code should be build when we
> > > have only a swrast driver.
> > > Can you try and kill that bug, or shall I?
> >
> > Isn't that what this patc
On Tue, 23 Apr 2019 at 23:10, Alyssa Ross wrote:
>
> > Off the top of my head - none of the VL code should be build when we
> > have only a swrast driver.
> > Can you try and kill that bug, or shall I?
>
> Isn't that what this patch does?
>
> If there's only swrast, this patch prevents enabling an
> Off the top of my head - none of the VL code should be build when we
> have only a swrast driver.
> Can you try and kill that bug, or shall I?
Isn't that what this patch does?
If there's only swrast, this patch prevents enabling any of the state
trackers, so need_gallium_vl won't be set, and VL
On Fri, 19 Apr 2019 at 19:53, Alyssa Ross wrote:
>
> The meson build system already has these checks. I've just copied them
> to autotools.
>
> Without this, state trackers could be enabled when building with the
> following set of options, which resulted in a compile error due to VL
> being built
The meson build system already has these checks. I've just copied them
to autotools.
Without this, state trackers could be enabled when building with the
following set of options, which resulted in a compile error due to VL
being built without DRM.
--enable-autotools
--with-platforms=x1
