On Sat, Jan 18, 2014 at 10:45:55PM -0800, Alan Coopersmith wrote: > Now that Xlib requires xcb to build, would it make sense to generate Xlib's > src/XErrorDB from the xcb proto xml files at build time? It would save > having to remember to update when extensions change (I just happened to notice > RANDR 1.4 was missing over a year after it shipped, and it doesn't look like > Keith added DRI3 or Present either).
Seems like a great idea. > Even more importantly, anyone want to try writing the script to do it? > > We would have to either save the ancient extension bits from XErrorDB to > append, > or decide it's okay to no longer give sensible errors to people doing > unsensible > things like trying to use XIE, DPS, & PEX with modern software. There's probably some value in having XCB XML descriptions of those extensions, even if XCB never builds a library to enable new callers of them. If nothing else, it would allow XCB-based protocol analyzers to analyze old software. But for a first pass, yeah, you could probably just drop all of those and nobody will notice. > Once that's done, we could then discuss reusing the code to build the X > server's > dix/registry.txt, but that would be adding new dependencies to the X server > build (though one we've long planned to someday have so we don't have to > forever > be fixing bugs in hand-written byte-swapping code). I don't see any problem with adding dependencies to the X server build that are already required to build XCB (and thus Xlib, and thus between the two of them all X clients). - Josh Triplett _______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
