I'm planning to add optional LIBMESH_DIR (and eventually LIBMESH_ARCH if we want to get fancy) variables to our example Makefiles. That can be a nice way to decouple the library source tree from application source trees, and since many people build their applications with a Makefile copied from one of the examples, it's good to provide flexible defaults.
So basically instead of: meshdir := ../.. We'll have: LIBMESH_DIR ?= ../.. Which sets the same option but gets overridden if there's already a LIBMESH_DIR environment variable. I'll also change LIBMESHRUN and LIBMESHOPTIONS to LIBMESH_RUN and LIBMESH_OPTIONS to add a little more consistency to our environment variable names. I've also wanted to factor together (into Make.common or a separate template) the shared parts of the example Makefiles. CFDLab alumni, see ~roystgnr/libmesh/svn/roy/common/ for the template my apps all use. But that may be excessive for now, especially since some of our examples get configuration options from individualized "make run" command line rather than just .in files. Any thoughts? --- Roy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
