On Mon, 3 Dec 2012, Kirk, Benjamin (JSC-EG311) wrote:

> It's a little frustrating there is not a configure-time way to
> detect these conflicts and avoid them - in the best case it results
> in a link-time error like in this Ubuntu case, more pathologically
> it is bizarre runtime behavior like this cppunit weirdness.

No kidding.

> I think I will add an option to not add those preprocessor macros, at least.

Make it non-default and that sounds like a fantastic idea.

BTW: with the multi-method support, is there any way to do a "make
whatever" that only touches a subset of the methods?  It would be nice
to do a "METHOD=dbg make run_examples" or a "METHOD=devel make -C
tests check" without triggering tests on every other build method too.
---
Roy

------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
BUILD Helping you discover the best ways to construct your parallel projects.
http://goparallel.sourceforge.net
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to