[Mesa-dev] Split libGLU into its own repository?

Jakob Bornecrantz jakob at vmware.com
Mon Jan 23 06:20:35 PST 2012


----- Original Message -----
> A while back, we split off GLw into a separate repository.  The
> rationale was that GLw should be maintained and released
> independently from Mesa/Gallium since it hardly ever changes and
> isn't closely tied to the core GL and drivers.
> 
> I'd like to do the same for libGLU.  I've split it out, created an
> new autotools build system, and uploaded a repository here:
> 
> git://people.freedesktop.org/~kwg/glu
>
> It has all the history except for some old build system vestiges,
> which filter-branch ate when I moved files from src/glu to the
> top-level directory.  I doubt anyone cares about those, since you
> obviously couldn't use the old build system anyway.

I prefer it if you kept at least the src/ folder, keeping it in line
with the other mesa source trees.

> 
> I made the installed library libGLU.so.1.3.1, as this ought to be
> compatible with existing binaries.
> 
> If this sounds good to everyone, we can create an official /mesa/glu
> repo and I can go ahead and remove it from the Mesa tree.  We'll also
> want to cut a glu release (though it could possibly wait until Mesa
> 8.1.)

I'm happy to see this go out, this looks like that last bit of code
that we can move out.

> 
> One concern I have is that libGLU in Mesa appears to have some build
> system magic for linking against OSMesa instead of libGL.  With the
> new system, I think you would need "pkg-config --libs --cflags gl"
> to report OSMesa.  I'm not sure whether that's an issue or not.

That said, I like this issue to be resolved before apply the patch, I
think you need to hunt down one of our OSMesa users and ask them to
try it out.

Cheers, Jakob.


More information about the mesa-dev mailing list