Hi there! 🙂

@kislinsk Do you have any opinion regarding this issue ?

Pushed new branch T26150-MergeAgainWithCherryPicks.

Pushed new branch T26157-FixMacOSInstaller.

Okay, all the Qt-related startup errors are fixed. But, on some PCs there is still the following one-time error even without --BlueBerry.clean:

• Fall back to classic versioning if MITK_REVISION_DESC is not set (I guess when building MITK from the source tarball)...

Pushed new branch T26152-PreciseVersioning.

Uh, I'm carefully optimistic that this really fixed the start of the MitkWorkbench. :-) Will test on Monday at another Ubuntu machine that has/had the Qt version mismatch error.

There's more going on on a clean Ubuntu 18.04 VM with GCC and starting MitkWorkbench for the first time. Basically no plugin is able to start because of broken linkage to libQt5Svg. That's probably a hot candidate for the version mismatch error on systems with a system version of that lib.

Pushed new branch T26150-UbuntuGCCWorkbenchStart.

Pushed new branch T26100-FixOrderOfVariables.

Thank you! 👍🏻

Added a simple check for the dimension. I will have to take a closer look at the 4D (maybe 2D) support in the next weeks unless there are volunteers who can take more care of it.

Pushed new branch T25798-FixDICOMSegWriterConfidenceLevelCheck.

TODO: Paths in MITK_EXTENSION_DIRS should be in canonical form, i.e., a backslash crashes the plugin list parsing of CTK which we are using.

Merged into master but not yet into releases/2018-04 until it was tested more thoroughly with Diffusion.

Looks promising, I completely moved all Diffusion code into a seperate directory and built the DiffusionRelease configuration. Double checking with @neher next week, testing Linux, macOS, and installers.

Status update: currently testing with MITK Diffusion as extension.

Pushed new branch T26100-ApplicationExtensions.

Pushed new branch T26099-BuildConfigurationExtensions.

Pushed new branch T25944-UpgradePocoToVersion1.9.