https://bugs.freedesktop.org/show_bug.cgi?id=94086
--- Comment #5 from Chuck Atkins <chuck.atk...@kitware.com> ---
So, based on our discussion, I believe I've addressed this in the attached
patch now by adding an --enable-gallium-xlib-glx option to specify gallium or
classic xlib-glx implementation. I gave it this behavior instead of the osmesa
approach of --enable-xlib-glx and --enable-gallium-xlib-glx being competing
options in order to stay consistent with how the other GLX options work; i.e.
--enable-foo turns on foo with default bar1 implementation and
--enable-bar2-foo changes the implementation to bar2. Invalid configurations
for enabling the gallium-xlib-glx implementation will produce configure errors
but there is no conflicting way to specify both classic and gallium xlib-glx
implementations.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
