On Jun 1, 2012 12:13 PM, "Brad King" <brad.k...@kitware.com> wrote: > > Teach 'configure' to read the default GL_LIB, GLU_LIB, and OSMESA_LIB > values from the environment. This allows one to mangle the library > names (without also mangling the symbol names) to make them distinct > from other GL libraries on the system. > --- > > On 06/01/2012 10:06 AM, Brian Paul wrote: > > You should transition to using autoconf > > One feature I used in the pure-make build system was to create a custom > configs/current to set GL_LIB, GLU_LIB, and OSMESA_LIB to have a "Mesa" > prefix. This helps ensure that VTK both builds and runs against my > nightly Mesa build regardless of what other "GL" libraries appear in > the dynamic loader's search path. With this patch I can run > > $ GL_LIB=MesaGL GLU_LIB=MesaGLU OSMESA_LIB=MesaOSMesa ./autogen.sh ... > > to build with custom library names. Please review. > > Thanks, > -Brad > > configure.ac | 17 ++++++++++------- > 1 file changed, 10 insertions(+), 7 deletions(-) > > diff --git a/configure.ac b/configure.ac > index 9fb8149..7f6ba96 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -355,6 +355,12 @@ else > LIB_EXTENSION='so' ;; > esac > fi > +AC_ARG_VAR([GL_LIB],[name of GL library @<:@default=GL@:>@]) > +AC_ARG_VAR([GLU_LIB],[name of GLU library @<:@default=GLU@:>@]) > +AC_ARG_VAR([OSMESA_LIB],[name of OSMesa library @<:@default=OSMesa@:>@]) > +GL_LIB="${GL_LIB-GL}" > +GLU_LIB="${GLU_LIB-GLU}" > +OSMESA_LIB="${OSMESA_LIB-OSMesa}"
I don't think this part is necessary. AC_ARG_VAR does this already. The rest makes sense though. Dan
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev