[Mesa-dev] [Mesa3d-dev] Separate demos repository
jfonseca at vmware.com
Wed Apr 21 15:08:57 PDT 2010
Apart of a minor details, I think we all agreed on general idea of
splinting the demos.
Could we have this repo in git://anongit.freedesktop.org/mesa/demos,
with or without the full history, so that we can all collaborate on
In particular I'd like to get the demos building for windows again.
On Wed, 2010-03-24 at 15:11 -0700, Eric Anholt wrote:
> People that hang out on IRC have probably heard about my build system
> work. One of the first steps I've been working on finishing is
> splitting out the demos repository. We're currently distributing the
> Mesa progs/ separately from the main Mesa distribution, and most people
> aren't installing it, so from a distribution perspective it doesn't make
> sense to be in the same repository. On the other hand, for driver
> developers that are having to make clean on a regular basis, wiping out
> the programs (if you even use them) doesn't help since the programs
> aren't really changing. And if they are, when you're bisecting around
> trying an app, you don't want the app changing at the same time.
> So, I've made a branch in my Mesa repository for a split of the progs/
> From Mesa.
> git://people.freedesktop.org/~anholt/mesa on the mesa-demos branch
> Open issues:
> Right now they don't install in general, but it would be easy to change
> if people are interested in a package that does. I've tested a bunch of
> them in tree and they seem fine.
> I've only tested the build on Linux with GL. The GLES stuff needs to
> get hooked up (I don't see a GLES implementation to test against or I
> would have).
> I don't know what to do about the progs/gallium. progs/gallium/unit
> looks like it should probably live in the Mesa tree next to the code
> that it's unit testing. progs/gallium/python/ though?
> None of the GLEW or GLUT is brought along with the apps. It looks to me
> like all OSes should have libGLEW and libfreeglut reasonably available.
> I'm not sure if we want the repository to contain all of previous Mesa
> history. Right now that history costs 145MB on disk for a deep
> checkout. If that's a problem for people, we could use the same tool
> that xcb did whose name I forget to to construct a history of just
> Where to go from here:
> If there isn't violent objection to this, I want to get this into place
> in /git/mesa/demos in a couple of weeks, and then remove those
> components from the main Mesa repository, plus the things that are only
> in there because progs depend on them (GLUT, GLEW).
More information about the mesa-dev