On Tue, 21 Nov 2017, Sven Schreiber wrote:
Am 21.11.2017 um 13:23 schrieb Dirk Eddelbuettel:
> I _could_ change the standard build to always use openmpi. May open yet
> another can of worms, but at least it is less involved.
Yes, why not? The only real downside would be additional dependencies, right?
Are there any cases (architectures etc.) where those dependencies would fail
which would then block installation of gretl? Or could openmpi become a
package suggestion instead of a dependency?
The openmpi library is in the nature of an "optional dependency" for
gretl.
When gretl is built with MPI support an extra CLI executable is
compiled (gretlmpi) alongside the regular GUI and CLI binaries.
This extra binary won't run unless the user has openmpi installed, but
the regular ones work as usual with or without openmpi on the system.
So I don't think one loses anything by including MPI aupport in the
build by default (as we do for MS Windows). A user without any MPI
library just has an extra binary that won't work unless/until they
install MPI.
Allin