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" But I think to really get that level of flexibility we'd want to go whole-hog and finally move libMesh to automake, not try to reinvent it. --- Roy ------------------------------------------------------------------------------ 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
