On Thu, Jul 18, 2019 at 7:19 AM Alyssa Ross <h...@alyssa.is> 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 the virgl and svga gallium drivers, even when > unsupported due to building with EGL and no compatible platform.
Today with "auto" you'll get some error message if a driver cannot be built because of a missing library, right? What happens after your patch? Is the user informed that some driver included in the "auto" set is not going to be built because of a missing library? It doesn't seem like it, unless I'm missing something, and that seems potentially worse than giving an error. I think automatic selection of build targets really breaks down when you have as many options and dependencies as we have. _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
