That's useful. Thank you.
It sounds like, as long as the component exists for OpenMPI already, it's
just a matter of compiling OpenMPI on a machine that has the headers and
libraries (with appropriate configure flags), and grabbing the individual
component from there.
-Sean
--
Sean Ahern
Computa
Here’s a link on how to create components:
https://github.com/open-mpi/ompi/wiki/devel-CreateComponent
and if you want to create a completely new framework:
https://github.com/open-mpi/ompi/wiki/devel-CreateFramework
If you want to distribute a proprietary plugin, you first develop and build it
Thanks. That's what I expected and hoped. But is there a pointer about how
to get started? If I've got an existing OpenMPI build, what's the process
to get a new MCA plugin built with a new set of header files?
(I'm a bit surprised only header files are necessary. Shouldn't the plugin
require at l
You don’t need any of the hardware - you just need the headers. Things like
libfabric and libibverbs are all publicly available, and so you can build all
that support even if you cannot run it on your machine.
Once your customer installs the binary, the various plugins will check for
their requ
There's been discussion on the OpenMPI list recently about static linking
of OpenMPI with all of the desired MCAs in it. I've got the opposite
question. I'd like to add MCAs later on to an already-compiled version of
OpenMPI and am not quite sure how to do it.
Let me summarize. We've got a commerc
