On 3/3/11 11:15 AM, Roy Stogner wrote: > > On Thu, 3 Mar 2011, Boyce Griffith wrote: > >> Because I think it is in general hard to detect robustly whether you >> can "safely" switch between PETSC_ARCH'es without doing a full >> recompilation, a nice compromise might be to be able to associate >> different PETSC_DIR/PETSC_ARCH values with different libMesh build >> modes. At least, this a feature that I would use. > > In general this is starting to sound like the "buildroot" support I've > been quite impressed by in a few of my group's application codes: > > "mkdir opt && cd opt && ../configure --with-opt-stuff && make && cd .." > "mkdir debug && cd debug && ../configure --with-debug-stuff && make"
You also can easily do these sorts of" VPATH" builds with Autoconf/Automake-based build systems. But, as I'm sure you already know, everyone hates Autoconf/Automake. ;-) This might be a dopey suggestion, but, sticking with the current build system, what if PETSC_DIR/PETSC_ARCH were not hardcoded, but if instead the values of PETSC_DIR/PETSC_ARCH were cached in some configuration file the first time that make is invoked with a particular build METHOD. In subsequent invocations with that same METHOD, if the cached values to not match the current settings for these environment variables, then either a warning or an error message is emitted. -- Boyce ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
