On Dec 10, 2007 7:46 AM, Brian Paul <[EMAIL PROTECTED]> wrote: > > Dan Nicholson wrote: > > > > export CC=/bgl/BlueLight/ppcfloor/blrts-gnu/bin/powerpc-bgl-blrts-gnu-gcc > > export CXX=/bgl/BlueLight/ppcfloor/blrts-gnu/bin/powerpc-bgl-blrts-gnu-g++ > > export CFLAGS="-O3 -ansi -pedantic" > > export CXXFLAGS="-O3 -ansi -pedantic" > > > > ./configure --with-driver=osmesa --enable-static > > > > No new files, no hardcoding paths, takes the user's options, etc. > > Yes, but the above is basically a magical incantation that nobody would > have a clue about if it weren't explicitly documented. That's the kind > of situation in which a "pre-packed" config saves a lot of effort.
The only magical part of that is --with-driver=osmesa. Not counting ./configure --help, I plan to document the options in the html if this is accepted. However, the environment variables are completely standard and probably already set by the developer since that's the way you coordinate with all autoconf and make projects. If the bluegene developers need to use the compiler in /bgl/..., then they'll know that. We don't need to hardcode that into mesa's git tree. I also don't think --enable-static is less intuitive than "MKLIB_OPTIONS = -static" :) I'll stop arguing now :) -- Dan ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
