Boyce Griffith
2017-05-25 01:52:26 UTC
I am working on the build system for IBAMR (https://github.com/IBAMR/IBAMR),
and we are automating building IBAMR's dependencies -- including libMesh.
I want to confirm that I am using the "--with-methods" configure flag
correctly.
I am under the impression that if we configure libMesh with the argument
"--with-methods=dbg", that the METHOD environment variable need not be set
because when we run `make` only the debug version of the library will be
built.
Is that correct? Or should both be set?
On the libMesh side, it's correct that if you use METHODS=dbg orand we are automating building IBAMR's dependencies -- including libMesh.
I want to confirm that I am using the "--with-methods" configure flag
correctly.
I am under the impression that if we configure libMesh with the argument
"--with-methods=dbg", that the METHOD environment variable need not be set
because when we run `make` only the debug version of the library will be
built.
Is that correct? Or should both be set?
--with-method=dbg, libMesh will only build dbg mode.
On the application side, I can't speak for IBAMR, but none of the
other libMesh-based-frameworks I've used will try to autodetect which
methods are available; they'll just fail at link time if you try to
build against a method which the current libMesh install doesn't
provide. That's probably a good thing, IMHO; it's better form to tell
the user when they've asked for something inconsistent, rather than to
try and guess what they really meant.
(Elijah, it might be a good idea to have an optional flag that lets users say which libMesh method to use, and to default to dbg for debugging builds and to opt for non-debugging builds.)