The auto wrapping functionality for MPISolverWrapper looks correct and straightforward to me. A check for function type is already included in the HyppopySolver.

I agree. As we already said, we have to work on the mpiplayground anyways and convert it into a propper mpi_example. I will spawn a task for that and include your suggestion there.

In rOBSHYPPOPY1358b14d22f999ffcb9b8d1dbe7d8adfac020ef6#167883, @floca wrote:

@kleina I think you should move the mpi playground stuff away from the top level. Examples would be better suited. Don't you think?

That makes a lot of sense. I personally like the idea of a "optional dependency" better. I will have a look.

I do. I can build the current develop and let you know, if something changed for me.

It was a clean build with MITK_BUILD_CONFIGURATION = WorkbenchRelease. I also enabled XNAT and only build "release". But I think that's all.

With the installer you send me it worked :-(
I fetched and pulled develop this morning. What else should I try to narrow it down?

AFAIK there is no special tutorial for QtCreator. The code should be the same, as it should (like MITK in general) work on both platforms.
In QtCreator, you select the project you want to build in the lower left corner where the "green play buttons" are.
For your specific question, you need to add cmd arguments when starting the project. Here is a stackoverflow post on how to do that, hope that helps: https://stackoverflow.com/questions/1593288/qtcreator-and-command-line-arguments

This is the error message, that was not there with the old installer:

What about the Segmentations? I was wrong, I tried with the current develop as well (sorry, was used to having the master branch on clone :-D).
I had Hanno also try it and the segmentations are missing for him as well.
I put an installer into the same folder, you can just start it from the bin folder to reproduce.

For Qt 5.12.5 it is OpenSSl 1.1.1

I made a short video. Sorry for the powerpoint thingy at the end... was to stupid to figure out how to stop the recording :-P:

According to Nina this is kind of a dealbreaker for her and really slows her down. I would give this one a high priority in BlackSwan context.

Here are the DLLs we used for the BlackSwan demo.

This issue can be solved by copying the following DLLs to the exe path of the workbench: