-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix build of parallel #242
Conversation
Should not |
0ddcb7f
to
52fab73
Compare
|
We merge like that? |
@@ -10,12 +10,12 @@ target_compile_definitions(HighFive INTERFACE ${HDF5_DEFINITIONS}) | |||
|
|||
# MPI | |||
if(HIGHFIVE_PARALLEL_HDF5) | |||
target_include_directories(HighFive SYSTEM INTERFACE ${MPI_C_INCLUDE_PATH}) | |||
target_link_libraries(HighFive INTERFACE ${MPI_C_LIBRARIES}) | |||
target_include_directories(HighFive SYSTEM INTERFACE ${MPI_CXX_INCLUDE_PATH}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were these changes required to it to succeed? Or is it just an improvement?
I believe not, it would be one more dependency. However, in our internal stack with Spack, yes, we should build with mpi by default. |
We now cover the scenarios of installing hdf5 / build HighFive: - serial / serial - parallel / parallel - parallel / serial
We should support the scenario added (using a parallel hdf5 but compile serial apps) |
Really good catch, I fix it but it's only that findHDF5 don't do its job well |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fix #241