DRAFT: Build with MPI wrappers only when --compiler is mpifort, mpif90, or mpif77 #1042
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When complete, this Pull Request (PR) will address #929 by making it possible for a project to build alternatively with or without the Message Passing Interface ([MPI]) wrappers.
To Do
Change
fpm
' behavior so that when the manifest [dependencies] block containsmpi = "*"
,fpm
builds with the MPI wrappers and links to the MPI bindings only whenthe
--compiler
argument ismpifort
,mpif90
, ormpif77
.mpi
as a metapackage only when the above condition is met.The first commit in this PR accomplishes the first checked item above. To see this capability in action, one can start a new
fpm
project viafpm new optional-mpi
and then adding the following lines to the manifestoptional-mpi/fpm.toml
:At the time of creating this daft PR, when the use of MPI is removed by a C-preprocessor macro such as in
building with the
mpi = '*"
terminates with an errorbecause
fpm
parses files for internal dependencies before running the preprocessor.