Dave Airlie wrote:
The GLX proto headers are all that is required from Xorg, otherwise
we end up with two copies that can get out of sync with each other..
the GL proto module is very small ....
I'm no expert on these things, but doesn't one of the header
locations define the library capabilities and the other the server
capabilities? Do their capablilities strictly need to match?
Or is the file used only for the server part of Mesa?
Nope they define the protocol between the client and server, so Mesa
requries the latest headers to get access to the protocol definitions
for the latest protocol,
OK, so there's a need for this approach during protocol development and
testing.
Still, IMHO it appears a little strange to me to check out a package
and then have to manually copy a file from another package to make it
build. Since, in particular, Mesa's libGL can be used for indirect
rendering against X servers other than Xorg, and even other indirect
rendering libraries than Xorg's default. Couldn't the Mesa copy be the
master, opening up for possible protocol extensions not yet supported by
Xorg?
Or use Keiths idea to build libGLCore within Mesa?
Then we don't find breakage until some time down the road, CVS is
development version, you want stable you build stable branches of
Xorg which work against stable Mesa branches..
Yes, but this is a breakage that will happen exceptionally often. In
fact as soon as somebody checks in a new file to a Mesa part that is
referenced by Xorg. If Xorg then is immediately updated, everybody
trying to build will have to update Mesa too. If the new commit is
buggy, a lot of developer's time is wasted.
My suggestion could boil down to whatever person updates the Mesa
building parts of Xorg makes a note in the wiki giving the current
Mesa version (Date and time) for which the update was made, so that
people checking out Mesa won't have to guess it as I had to do today.
That might be an idea... granted the xorg mailing list normally has a
patch within minutes of someone breaking it.. my other idea is to
automake'ise Mesa for Linux systems, then try and re-use the
Makefile.ams from Mesa in the Xserver build at least that'll stop
things getting out of sync..
That would indeed solve the Makefile sync problem.
/Thomas
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
