<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Multiple conflicting libGL libraries installed" href="https://bugs.freedesktop.org/show_bug.cgi?id=94086#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Multiple conflicting libGL libraries installed" href="https://bugs.freedesktop.org/show_bug.cgi?id=94086">bug 94086</a> from <a class="email" href="mailto:chuck.atkins@kitware.com" title="Chuck Atkins <chuck.atkins@kitware.com>"> Chuck Atkins</a> <pre>(In reply to Emil Velikov from <a href="show_bug.cgi?id=94086#c6">comment #6</a>) > 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. Just to be clear, before I re-work the patch, instead of enabling behavior as a set of cascading options, you'd rather see the three options as mutually exclusive at the top level, correct? --enable-glx = enable DRI GLX --enable-xlib-glx = enable classic Xlib GLX --enable-gallium-xlib-glx = enable gallium Xlib GLX > > 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). I'll push the next one to the list (In reply to Emil Velikov from <a href="show_bug.cgi?id=94086#c7">comment #7</a>) > Thanks for bringing this topic and working on the patch. I can realise it's > not the easiest/prettiest of things No it's not but it's far less frustrating to fix and then not have to deal with than to always have a hacked patch that has to get applied. I'd much rather tell a customer who asks "How do I build Mesa to work with ParaView" to just download the mesa source, configure this way, and build than to tell them download mesa, apply this weird patch to the build system that you have to get from us, then configure this way and build. As a developer at a company that produces open source software, I consider it just being a good citizen in the eco-system.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>