Re: [Mesa3d-dev] Adding Mesa support for 3.3.6 to XFree86

[Marcelo E. M. <mar...@bi...>]

>> "Mike A. Harris" <mh...@re...> writes:

 > For all of our XFree86 4.x releases, we have shipped XFree86 but
 > have replaced the Mesa that comes with it with the standalone
 > Mesa from the mesa3d project hacked to support DRI.
 > 
 > The reason for this is that we need software OpenGL working on
 > both 4.x and 3.3.6, and DRI hardware acceleration on 4.x.

 Hmmm... isn't this what Brian did?  Your problem is that the 3.3.6
 server doesn't have the GLX extension.  The proper hack ;-) is to teach
 the libGL in the XFree86 4 sources about fakeglx, and I'm under the
 impression Brian did this.

 > There were some oddball chicken and egg dependancy problems with
 > this solution, and so we've decided instead of having a separate
 > Mesa package, to take the Mesa package and fold it into the
 > XFree86 src.rpm.

 ugh.

 > Here is what would IMHO be the best - at least from my viewpoint
 > as a distributor/package maintainer:

 hi from one of the guys that has your job on the Debian side...

 > The easiest method (for me) would be if the Mesa that comes with
 > XFree86 had the 3.3.6 compatibility built right into it, and was
 > perhaps an Imake directive to enable at X build time
 > (BuildMesaSupport336?).  This would make our hack unnecessary,
 > and would make package maintenance much simpler as well.  I'd
 > much rather spend my time hacking on and contributing to XFree86
 > itself than on packaging nightmares in unfamiliar turf...  ;o)

 Again, your problem is that Mesa in the XFree86 4 sources doesn't work
 unless the Xserver knows about the GLX extension (IOW, you'll also have
 a problem with an XF4 server that doesn't have the GLX module
 installed).  Mesa works with 3.3.6 servers because it has a "fake" GLX
 inside it, that is, it nevers sends GLX requests to the server, but it
 handles all of that internally.

 And again, I think Brian already did the necessary work...  (I haven't
 really tested)

-- 
Marcelo