-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 17 July 2004 22:34, Jon Smirl wrote:
> What mesa code uses the lines protected by these defines? Building
> linux-dri does not use this code. In fact linux-dri doesn't even need
> the X11 headers to build.
>
> XFree86LOADER
> XFree86Server
> IN_MODULE
>
> If these are indeed protecting dead code some significant cleanup can
> be done. Looking in mesa/main/import.c many routines are IFDEF'd.

Any code so protected that isn't included as part of (one of) 
lib{dri,drm,glx,GLcore}.a in the X server, is dead code.  Which explains why 
linux-dri doesn't use that code, since linux-dri doesn't build the 
server-side modules.

GLcore is the tricky part, since that's the indirect renderer.  The rest of 
the modules probably don't overlap with the solo code at all.

In other words, those defines don't affect sharing *_dri.so between X and solo 
because those modules are never loaded by the X server.  Any code that's 
going to end up in the X server will be in the core or the software 
rasterizer as part of libGLcore, which I will eventually do away with.  In 
the meantime, if you're adding code that will make it into GLcore, wrap it 
with the X ifdefs for now; but this shouldn't affect the DRI drivers at all.

- - ajax
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA+fH1W4otUKDs0NMRAjmBAJ9difLbcuwqqkjIVQl/g8gXCrozKACgigIi
2HP1FGLhGgRh09vI04SvPzg=
=NZjs
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id040&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to