Ian Romanick wrote:
The DRI driver builds are currently toast in both trees. I'm working like mad to get the rest of my changes worked in, but I keep hitting road blocks. At times it feels like things were disigned with the primary goal of making this more difficult. I have to leave for a bit, but I should be able to fix up (some of) the rest of it tonight. I'm really sorry this is taking so long. :(
Builds in the DRI tree are working again. linux-dri, linux-dri-x86, and (AFAIK) linux-dri-x86-64 builds are working in the Mesa tree again. solo builds are still toast. From this point on, DRI_NEW_INTERFACE_ONLY builds are the only support DRI driver builds supported in the Mesa tree. The "old" interface is still supported in builds from the DRI tree.
The next step is to remove the one place where glxclient.h is still used (in dri_util.h). This means some clean-up is need in glcontextmodes.[ch]. That's the easy part. The harder part is dealing with the various GLX_ defines used around the code (mostly in glcontextmodes.c, but also other places). I'm thinking that we need to import a version of glxtokens.h into the Mesa tree. Does that sound acceptable to all involved?
After that, we need to get libdrm building in its own tree, and have the Mesa build use that. Once that's done, all of the dri_client tree can be removed.
The final step will "just" be to convert the miniglx to use the new interface... :)
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
