and the way of compiling dri Re: devel tree

[Felix Kühling]

This is how I usually build DRI:

X.org without any DriDrivers. I use the Mesa version included in
xc/extras. This way I get a slightly outdated libGL and liGLcore (server
side software rendering for indirect rendering). Then I build Mesa from
CVS HEAD with the target linux-dri-x86. This builds the bleeding edge
versions of the 3D drivers independently of Xorg. This way I can work
with the latest version of the 3D driver in Mesa HEAD and not worry
about breaking the Xorg build system.

BTW, the snapshot builds work in the same way.

AFAIK this procedure is also documented in detail in the DRI Wiki (see
http://dri.sourceforge.net/cgi-bin/moin.cgi/Building).

HTH,
  Felix

Am Fr, den 17.12.2004 schrieb Sergio Monteiro Basto um 22:05:
> On Fri, 2004-12-17 at 13:33 -0700, Brian Paul wrote: 
[snip]
> Mesa's CVS head/trunk code, of course. If I want test lastest dri code ,
> I need to compile xorg with Mesa's CVS head/trunk code.
> 
> the other 
> "the way to build the newest DRI 
> drivers is with the 'linux-dri-x86' target in Mesa CVS."
> give me 2 differents libGLs and libGLUs
> and what is the correct libGL ?
> 
> and GLUT why glut doesn't enter on xorg ?
> 
> Anyway, I think the DRI developers must understand, how Xorg compiles
> Mesa else there dri drives becomes uncompilable (at least in my $ARCH)
> or definitely dri drives are compiled out of Xorg, but in this case Mesa
> miss the building of libGLcore!, so don't see how is it possible.
> 
> just left me, the first choice :)
> end of though,
> Conclusion if you agree, we could create the "trunk2" one copy of xorg
> cvs with last Mesa. ie
> mv http://cvs.freedesktop.org/dri/xc to
> http://cvs.freedesktop.org/dri/xc.old
> 
> and copy http://cvs.freedesktop.org/xorg/xc to
> http://cvs.freedesktop.org/dri/xc
> 
> thanks for your time,
> 
[snip]

-- 
| Felix Kühling <fxkuehl at gmx.de>                     http://fxk.de.vu |
| PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3  B152 151C 5CC1 D888 E595 |