[Mesa-dev] [Bug 94086] Multiple conflicting libGL libraries installed
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Apr 14 16:04:19 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=94086
--- Comment #6 from Emil Velikov <emil.l.velikov at gmail.com> ---
(In reply to Chuck Atkins from comment #5)
> 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.
I'd rather not do that, as the current "enable foo when bar is on" feels quite
magic. Sometimes it gives you a warning although in all honestly, I doubt
(m)any people really look at those. I would really want to nuke them altogether
and make the configure shorter and cleaner.
A bunch of comments coming in a second, but for next round please send the
patch to the mesa-dev mailing list (ideally via git send-email).
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160414/b0fca193/attachment.html>
More information about the mesa-dev
mailing list