Thanks for getting back to me...

On Sat, Jan 19, 2013 at 4:37 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:

> 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.
>

Hmmm.... we did some testing with this this week and there are a couple of
issues:

1.  If you don't "make install" then Make.common does not get created
 (obviously not necessary for an example... but that is problematic for
some users).

2.  If you don't "make install" then bin/libmesh_config doesn't output the
proper include directories (or are we doing something wrong?).  Coupled
with #1 this means that not make installing doesn't seem to be an option
for actual application development... but are we missing something?

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.
>

Well, that assumes that your example is all working in the first place ;-)
 When developing a new example for a new feature I expect to do hundreds of
build/run cycles (probably including many debug runs as well) and most of
those won't work in someway...

But it is good to know.


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

I'll try to go back to not doing out of tree builds and see if I can get it
to work.  I really hope so!

Thanks again for the reply,

Derek
------------------------------------------------------------------------------
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