Re: [Mesa3d-users] OSMesa incompatible with other GL output methods?

[tom f. <tf...@al...>]

Owen Kaluza <Owe...@sc...> writes:
> On Tue, 2009-03-17 at 23:15 -0700, tom fogal wrote:
[snip]
> > See my recent work with respect to GLEW. In a sentence, you want to
> > 1) mangle all of Mesa's symbols, and 2) load all your OpenGL functions
> > at runtime. Details can be found in my posts to their mailing lists,
> > which should be findable with a bit of googling.
> 
> I looked up your posts, it looks like I would require a custom compiled
> osmesa library then?

Yes and no.  You need a custom compiled Mesa and potentially Mesa's GLU
lib (if you use GLU); the OSMesa library might change with mangling,
but I doubt it.  To do this, you just add "-DUSE_MGL_NAMESPACE"
to the CFLAGS when compiling Mesa.  I've been thinking of an
`--enable-mangling' autoconf switch for a while now, but haven't had
the time...

> If so it's probably not worth bothering from my point of view as it's
> easier for us to provide two versions or instructions for users to
> compile our stuff differently depending on their requirements.

Sure, if you know that beforehand.  The real trouble only comes in
if you run on a cluster && don't know which GL library to use until
runtime.

-tom