-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Keith Whitwell wrote: > On Mon, 2009-02-09 at 13:10 -0800, Dave Airlie wrote: >> On Mon, 9 Feb 2009, Kristian Høgsberg wrote: >> >>> On Mon, Feb 9, 2009 at 3:28 PM, Dan Nicholson <dbn.li...@gmail.com> wrote: >>>> On Mon, Feb 9, 2009 at 9:11 AM, Brian Paul <bri...@vmware.com> wrote: >>>>> In terms of the build system, we'll initially default to the non-gallium >>>>> build. To build with gallium I'll add some new configs like >>>>> 'linux-gallium'. >>>> I haven't tried building gallium at all, but is there interest in >>>> adding support to the autoconf goo? I don't know how well it would fit >>>> in with the current semantics (--enable-driver=...), but I could take >>>> a look. >>> I would definitely appreciate that. >> Maybe this is a dumb question, >> >> 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
I don't think people outside VMWare are using the build targets from configs any longer. I believe that most people are using the autoconf mechanism. > 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. If we're ending up with multiple, identically named drivers for the same hardware, we've already lost. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmSGiwACgkQX1gOwKyEAw+hSwCfavIWf+3IHZqmhRPE5ybSETMq Gj0AoJ1XSgMBbdMz9QhSnRpl9XGaNE1F =pI3H -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ 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
