The plugin idea is a good one, and probably your best option (e.g.,
have an MPI plugin and a non-MPI plugin). FWIW, plugins are the
foundation of Open MPI -- we determine which functionality is
available at run-time by opening plugins and querying them. Plugins
generally do one of the fol
I don't think there is an Open-MPI based solution for this.
I would probably to the following:
- place all functions using MPI calls into a separate module and
create a shared-object dynamic library (so file).
- create another .so file which contains the non-MPI equivalents of
those functions
At
Hello,
We have created a piece of software that is designed to work under a variety of
conditions, one of which is using MPI.
This application will preferably us a single executable and then load the mpi
communications interface as a library at runtime, however adding this
functionality by com
