Tests build with installed version of DAGMC if present about dagmc

[gonuke]

To make sure I understand: the solution would be to force all tests to use the headers from the build directory, right?

[pshriwise]

To make sure I understand: the solution would be to force all tests to use the headers from the build directory, right?

That would be my proposal, yes. I haven't looked at the CMake files, but I don't expect it would be a big change.

[ahnaf-tahmid-chowdhury]

One way to do this is by adding the build directory to the include path before the installation directory.

include_directories(${CMAKE_BINARY_DIR}/src/dagmc ${CMAKE_INSTALL_INCLUDEDIR})

Or, we can modify the tests themselves.

#include "${CMAKE_BINARY_DIR}/src/dagmc/DagMC.hpp"

[gonuke]

What if we add SET(CMAKE_INCLUDE_DIRECTORES_BEFORE ON)?

Seems like a big hammer, and surprised we haven't encountered it before, but should work?

[ahnaf-tahmid-chowdhury]

What if we add SET(CMAKE_INCLUDE_DIRECTORES_BEFORE ON)?

Seems like a big hammer, and surprised we haven't encountered it before, but should work?

According to my knowledge, DAGMC depends on third-party libraries installed in the system include directories. So, if these libraries have conflicting versions or headers with DAGMC, this could lead to unexpected behavior or compilation errors. However, we can resolve that by testing DAGMC in different build environments (Geant4, OpenMC, PyNE etc) to ensure that it works as expected.

[gonuke]

But for the purpose of testing we probably always want the most local headers, right?

[ahnaf-tahmid-chowdhury]

But for the purpose of testing we probably always want the most local headers, right?

Yes, it is usually best to use the most local headers to ensure that the tests are using the correct version of the code.

Setting CMAKE_INCLUDE_DIRECTORIES_BEFORE to ON can be one way to achieve this, but as I mentioned earlier, it can have unintended consequences if not used carefully.