On Nov 20, 2012, at 2:23 PM, Benjamin S. Kirk <benjamin.k...@nasa.gov> wrote:
> > On Nov 20, 2012, at 3:06 PM, John Peterson <jwpeter...@gmail.com> wrote: > >> On Mon, Nov 19, 2012 at 1:56 PM, Kirk, Benjamin (JSC-EG311) >> <benjamin.kir...@nasa.gov> wrote: >>> My feeling is installing them with a couple line makefile would be better - >>> >>> $ cp -r /libmesh/example ./myexample >>> >>> make & play >>> >>> encourages more learning anyway. >> >> Yeah, I agree we don't really need the binaries but the installed >> examples are pretty useless if we don't also install a Makefile with >> them… > > Indeed. All the Makefile.old's are there, I will use these as the basis of > an installed Makefile that uses libmesh-config to get the relevant configure > bits. I don't want to encourage new users to include Make.common as a way to > get at the configuration. With r6433 we install a common makefile and the run script with each example, so the following works: assume I install into /tmp/foo: $ make && make install $ export LIBMESH_DIR=/tmp/foo $ cd $LIBMESH_DIR/examples $ for dir in */* ; do cd $dir ; make ; sh ./run.sh ; cd - ; done This installs $srcdir/contrib/utils/Makefile and the case-specific run.sh in the example directory. The idea is the user can copy a given example and start hacking. I'd like to rework the makefile not to include Make.common, and that means moving the compile rules into it directly. I'd also like to get some feedback on this approach since these self-contained examples should be the way people get introduced to the library, and I want to set good 'best practices' with the Makefile! -Ben ------------------------------------------------------------------------------ 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
