On Wed, 21 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote:
Mostly because 'include our makefile' is frowned upon…
Right - but it wouldn't be "our makefile", with a billion
internally-used identifiers and things that might break other build
systems; it would be "our provided make rules", specifically designed
to be the core of a build system.
We have time to iterate this though, not like I want to ship 0.9.0
tomorrow!
Certainly. If we're brainstorming wishlist-y, I'd actually like to
provide multiple examples of *build systems* too - one a two-part
Makefile with a stripped down "Make.common" that does a better job of
separating PETSc/SLEPc/libMesh/etc internals from deliberately
provided (and LIBMESH_ prefixed) variables, one a barebones
Makefile.am setup; even an scons or more exotic option if people
wanted to contribute those.
---
Roy
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
