In a few places, a preprocessor directive defined as DEBUG is being used. We only use this for debugging purposes, and it turns out that if we want to have those code paths turned on in other libraries we might run into issues. I ran into this within ExaConstit when trying to take advantage of MFEMv4.1 and make use of a debug build where the DEBUG directive is made use of. MFEM makes use of an enum with a DEBUG named field which is causing issues with this debug directive being passed into the compiler for ExaConstit. Therefore, I say we rename DEBUG to something like ECMECH_DEBUG.
In a few places, a preprocessor directive defined as
DEBUG
is being used. We only use this for debugging purposes, and it turns out that if we want to have those code paths turned on in other libraries we might run into issues. I ran into this withinExaConstit
when trying to take advantage of MFEMv4.1 and make use of a debug build where theDEBUG
directive is made use of. MFEM makes use of an enum with a DEBUG named field which is causing issues with this debug directive being passed into the compiler forExaConstit
. Therefore, I say we renameDEBUG
to something likeECMECH_DEBUG
.Thoughts @nrbarton ?