Thomas Hellström wrote:
Keith Whitwell wrote:

This seems to be:

https://bugs.freedesktop.org/show_bug.cgi?id=5873

Which says:
-----
You need glxproto.h from the X.Org proto/GL CVS module to build current Mesa CVS.
-----

I'm not personally much of an expert regarding these things... It does seem like we've ended up with some odd interdependencies between projects.

Keith

Indeed. Mesa CVS won't build without files from Xorg CVS, and Xorg CVS doesn't build because of updates to Mesa shader 48 hrs ago.

Shouldn't Mesa be able to build as a standalone glx-capable libGL?

Also, Xorg should define and document a Mesa version to build against. Commiting new files to Mesa breaks Xorg building. Currently the Xorg modular wiki page says Mesa CVS is needed to build Xorg CVS.

It seems to me that whatever reason Xorg needs to build mesa for (I'm guessing the indirect GLX software rasterizer) is a mistake.

If mesa is to be built, it should be built within the tree it is developed. That might mean that Mesa should learn how to build itself in a form suitable for use as X.org's internal rasterizer, or better still now that we have AIGLX approaching, that Mesa grows a DRI software-only rasterizer that Xorg can use when a hardware driver for AIGLX isn't available.

Keith


-------------------------------------------------------
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

Reply via email to