On Thu, Jul 18, 2019 at 7:19 AM Alyssa Ross wrote:
>
> "auto" pays attention to the OS and architecture of the target system,
> but not the available libraries. If, say, libdrm isn't available, "auto"
> won't work, and a manual list of drivers will be required anyway. It
> would also try building
Quoting Alyssa Ross (2019-07-18 10:29:45)
> > For virgl/svga: I'd be inclined not to build them automatically. They're not
> > useful outside of a VM, so most developers either will be exclusively
> > building
> > one (not both) of those, or not be interested in them at all. And Distros
> >
> For virgl/svga: I'd be inclined not to build them automatically. They're not
> useful outside of a VM, so most developers either will be exclusively building
> one (not both) of those, or not be interested in them at all. And Distros
> don't
> use auto options so we don't need to worry about
Quoting Alyssa Ross (2019-07-18 07:15:14)
> "auto" pays attention to the OS and architecture of the target system,
> but not the available libraries. If, say, libdrm isn't available, "auto"
> won't work, and a manual list of drivers will be required anyway. It
> would also try building the virgl
"auto" pays attention to the OS and architecture of the target system,
but not the available libraries. If, say, libdrm isn't available, "auto"
won't work, and a manual list of drivers will be required anyway. It
would also try building the virgl and svga gallium drivers, even when
unsupported due
