I think the correct solution is to make the two conflicting libs mutually exclusive. If both are enabled in the build at the same time, then let's print a configure error. I don't think installing a lib to a non-standard directory like /usr/lib/gallium would help anybody.
Marek On Thu, Aug 22, 2013 at 1:03 AM, Matt Turner <matts...@gmail.com> wrote: > On Wed, Aug 21, 2013 at 7:06 AM, Brian Paul <bri...@vmware.com> wrote: >> On 08/20/2013 03:18 PM, Matt Turner wrote: >>> >>> The Gallium implementation is apparently not ready for regular >>> consumption, so as much as I hate adding more build-time options, here's >>> another. >>> >> >> The intention was for the old/swrast version of OSMesa would wind up in lib/ >> while the gallium version would wind up in lib/gallium/. I thought that's >> what I implemented. Or is it "make install" that's causing overwriting? > > Yes, it's make install that's overwriting the old/swrast version with > the Gallium version if Gallium is enabled. What winds up in the lib > directory when just make is run is controlled by the all-local hook > that creates the symlinks. > > If you want it installed to $(libdir)/gallium the > src/gallium/targets/osmesa/Makefile.am should look like > > gallium_libdir = $(libdir)/gallium > gallium_LTLIBRARIES = lib@OSMESA_LIB@.la > > libgl-xlib has this same problem. > > Should I send a patch for that? > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/mesa-dev _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
