Skip to content
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

Make MPI optional #80

Open
fluidnumerics-joe opened this issue Nov 24, 2024 · 0 comments
Open

Make MPI optional #80

fluidnumerics-joe opened this issue Nov 24, 2024 · 0 comments

Comments

@fluidnumerics-joe
Copy link
Member

To help lower the barrier to entry, we want to make MPI an optional feature. This will require splitting modules that use MPI calls into single process components and multi-process components. If MPI is detected, then we ought to build MPI enabled libraries in addition to the single process libs.

This will ultimately necessitate breaking up the library artifacts that are created into a few groups

  • selfcore
  • self_[cpu-arch]
  • self_[cpu-arch]_mpi
  • self_[cpu-arch]_[gpu-arch]
  • self_[cpu-arch]_[gpu-arch]_mpi

When users build applications with self, the intention would be to link against -lselfcore and the appropriate library for the architecture they want to build for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant