Skip to content
Snippets Groups Projects

Add a dirty trick to find/test PETSc

Merged Stéphane Del Pino requested to merge feature/petsc into develop
2 files
+ 17
1
Compare changes
  • Side-by-side
  • Inline
Files
2
@@ -278,7 +278,14 @@ int main(int argc,char *argv[]) {
return 0;
}
")
multipass_source_runs ("${includes}" "${libraries}" "${_PETSC_TEST_SOURCE}" ${runs} "${PETSC_LANGUAGE_BINDINGS}")
multipass_source_runs(
"${includes} ${MPI_CXX_INCLUDE_DIRS} ${MPI_CXX_COMPILER_INCLUDE_DIRS}"
"${libraries}"
"${_PETSC_TEST_SOURCE}"
${runs}
"${PETSC_LANGUAGE_BINDINGS}"
)
if (${${runs}})
set (PETSC_EXECUTABLE_RUNS "YES" CACHE BOOL
"Can the system successfully run a PETSc executable? This variable can be manually set to \"YES\" to force CMake to accept a given PETSc configuration, but this will almost always result in a broken build. If you change PETSC_DIR, PETSC_ARCH, or PETSC_CURRENT you would have to reset this variable." FORCE)
Loading