On Jan 19, 2013, at 5:26 PM, Derek Gaston <fried...@gmail.com> wrote:

> So, here's my workflow for adding a new example (in a new examples directory).
> 
> cd libmesh/examples
> mkdir mesh_transfer
> cp -r introduction/introduction_ex3 mesh_transfer/simple_dtk
> cd mesh_transfer/simple_dtk
> # Rename files to simple_dtk (or whatever)
> # Edit Makefile.am to include the name of the new files
> cd ../..
> # Edit Makefile.am to include new directory
> cd .. (to the "libmesh" directory)
> # Edit configure.ac to include the new example's Makefile
> ./bootstrap

Yes to here.

> mkdir build

You do not to build in a separate directory unless you want to.  I do this so I 
can use many different compilers on a number of machines that all share the 
same source tree on my shared linux filesystem, but I build in the top 
directory on my mac.

> cd build
> METHODS="opt dbg" ../configure --prefix=$LIBMESH_ROOT/installed
> make

Yes, caveat the ../configure …  as noted above.

Also, if you want a shortcut to reconfigure with your last options just use

./config.status --recheck

In fact, if you boostrap and forget to reconfigure your next 'make' should do 
it for you.

> make install

Not required to test your example.  You can now run your new example through 
our 'make check' target, without ever installing anything.  For example:

make -C examples//mesh_transfer/simple_dtk check

will build and run your example from the source tree.

So with that workflow, your one terminal should suffice from here….

-Ben


------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to