On Tue, 2009-02-10 at 05:41 -0800, Jakob Bornecrantz wrote: > On 10 feb 2009, at 13.39, Keith Whitwell wrote: > > On Tue, 2009-02-10 at 04:21 -0800, Jakob Bornecrantz wrote: > >> On 10 feb 2009, at 08.17, Michel Dänzer wrote: > >>> On Tue, 2009-02-10 at 01:57 +0100, Anders Juel Jensen wrote: > >>>> On Monday 09 February 2009 22:15:44 Keith Whitwell wrote: > >>>>>> but is it possible to build both gallium drivers and classic > >>>>>> drivers from > >>>>>> the same tree at the same time? > >>>>>> > >>>>>> or is distro life going to be made shit yet again. > >>>>> > >>>>> Anything's possible -- I guess I'm not clear on which is > >>>>> preferable, so > >>>>> feedback is welcome. > >>>>> > >>>>> We can do either: > >>>>> - have some new build targets, like "linux-gallium-dri" etc, that > >>>>> build the drivers and put them in mesa/lib/xyz_dri.so > >>>>> or > >>>>> - build both lots of drivers, and put the gallium ones in a new > >>>>> directory, like mesa/lib/gallium/xyz_dri.so > >>>>> > >>>>> Note that there are going to be multiple, different copies of > >>>>> xyz_dri.so > >>>>> in the second approach. > >>>>> > >>>>> Is there a third option? > >>>>> > >>>>> Keith > >>>> > >>>> It would be nice if it was possible to have both installed, and an > >>>> easy way to > >>>> switch between them in xorg.conf > >>> > >>> It's always been easier than that: Just point $LIBGL_DRIVERS_PATH to > >>> the > >>> directory (directories) containing the driver you want to use. Each > >>> application can use a different driver (of course, the 3D driver has > >>> to > >>> be compatible with the X driver). > >> > >> It should definitely possible to build both at the same time > >> especially now that the gallium intel dri drivers use the same drm as > >> the legacy intel dri drivers. I think that even the nouveau use the > >> same drm. > >> > >> Brian I have a patch on gallium-xorg-driver that lets us more fine > >> tune the building of the gallium dri drivers. Is it okay if I revert: > >> "mesa: added new linux-gallium and linux-gallium-debug configs" [1] > >> from gallium-master-merge and apply: > >> "gallium: Introduce new subdirs build variables" [2] > >> from the gallium-xorg-driver branch? > > > > I think I'd prefer either building all or none of the drivers in each > > case, rather than trying to tweak things up or down driver by driver. > > Well we need to pick the drivers that can actually be built with drm > master. And currently having only DRI_DIRS is not enough since the > radeon pipe and winsys doesn't build doesn't but the legacy version > does.
I'm not advocating turning on drivers that don't build by default. > Which is why the subdirs commit is needed. It is also needed because > it allows us to select state_trackers, since currently it is hard > coded to glx in the Makefile. In the future we will need to select > DRI1/2 ones to, but only for the linux-dri builds. > > > > > > > Given Dave's preference for building both legacy + gallium drivers > > from > > the existing linux-dri-* targets, I'd suggest adding some > > subdirectories > > to mesa/lib, along the lines of: > > > > mesa/lib > > mesa/lib/dri > > mesa/lib/gallium > > > > and having the build drivers land in one subdirectory or the other. > > Distros or whoever can then pluck out the ones they care about from > > either directory. > > I am totally for this idea. The commit I proposed didn't solve this it > solved something else. I can whip up a patch which does this. It sounds like we may have been talking at cross purposes. This is the only point I was trying to make & it seems we're in agreement. Keith ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
