Around 17 o'clock on Nov 12, Brian Paul wrote:
Yeah, the issue is that libGL has dependencies on the internals of libX11.
Can you easily enumerate what non-public interfaces you're using from Xlib? If libGL uses them, they are defacto public interfaces and so should be published and standardized so that binary compatibility can be assured with changes in Xlib.
I've already discovered that several existing X extension libraries use the internal region representation and so now include region.h as part of the public Xlib interface. Building things as separate modules enforces a certain level of rigor in interface specification that has been lacking in the monolithic environment.
I think it's mainly things in Xlibint.h like _XRead(), GetReq(), GetReqExtra(), LockDisplay(), SyncHandle(), etc. Everything that's needed for sending/recieving X protocol.
Is Xlibint.h considered a public interface for the purpose of extension libraries?
-Brian
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
