The implementors should speak up about the details but yes, that would be the simplest mechanism. If static linking is preferred for performance reasons, it should be possible to link the application to the morph library to MPI at installation time. In this case the morph library can be compiled into multiple variants, one for each target MPI type and the application would link to the morph layer object files for the local MPI. The resulting application would then need to be relinked in order to use another MPI but there would be no need to recompile either the application or the morph layer.I may have missed this in the trail, but I'm still unclear as to how a morph layer loads the target library. Is this dlopen()?