(crap, thought I sent this!!)
> Ben, Paul, would you mind if I changed the macros like > CONFIGURE_EXODUS to take "if-true" and "if-false" arguments (like e.g. > $2 and $3 in AX_BOOST_BASE), then move anything libmesh.automake > specific (e.g. AC_CONFIG_FILES calls) into their caller macro > (probably libmesh_optional_packages.m4)? We ought to be able to sync > most of these up with trunk m4/ (and share them with other projects) > after that small refactoring. That would be fine with me. Although I do like building up the single libmesh_optional_INCLUDES libmesh_optional_LIBS etc... The intent is to reduce the overhead of adding and maintaining additional packages by only modifying those variables. So if you can think of a clean way to maintain that (maybe that variable expansion gets rolled back into the calling macro?) then I'm all for it. -Ben ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
