Thanks for noticing. The new Boost.cmake script will support all four CMake build configurations.

Boost stopped to support newer toolset versions than 14.1 for the time being as they are binary compatible in the 14.x range. The new Boost.cmake script will be based on major versions to be at least minimum future-proof for 15.0 and upwards.

MITK_PP_ macros were replaced with their original BOOST_PP_ counterparts. Only mitkPPArgCount.h is left as it doesn't originate from Boost.

Pushed new branch T24615-FixBoostRelatedIssues.

Fixed in beta branch. Turned out it wasn't found on Linux and macOS at least since 2013. I just double-checked the 2016.11 installers and storescp was set manually back then.

Pushed new branch T25526-DoubleClickOnLabelItemCrash.

This error occurs when double-clicking on a label (no need for a second label to be present), or when searching for a label. Both code paths end in a request to update the label's center of the mass which is currently not compiled for four-dimensional images.

The single-step increase/decrease feature is in the beta branch now. I'll create subtasks for remaining TODOs.

Probably found the origin of issue. We're calling booststrap.bat on Windows and bootstrap.sh on other platforms. The latter script has lots of parameters like --with-toolset=..., while the former script just knows a single parameter like vc141. However, we currently assume that the former script would also understand --with-toolset=v141. The script doesn't know how to handle this and falls back to something else.

Pushed new branch T25435-TimeFunctionForSegmentationBasedOnBetaBranch.

Please re-open if I made wrong assumptions:

It would also be much more convenient if our build script would detect a thirdparty toolkit upgrade and remove the old version first before installing the new version. This is something that has to be done manually at the moment and it sucks big time to do this for all the remote continuous dart clients for example.

@tsvetkov is currently working on this task. Did you guys coordinate? :-)

What's the status on this one?

Lower priority as nothing happened so far.

Currently fixed with workaround, hence no pressing issue. Set priority to low but add #community_day tag.

Should work in 2018.04 (beta). Minimum recommended version for macOS in now High Sierra. Mojave works as well.

Found same leak also in mitk::DICOMSegmentationPropertyHelper.

Pushed new branch T25495-MemoryLeak.

I (hopefully) improved our CMake script by hint find_package(Qt5) at Qt default install locations (C:/Qt). Only MSVC for now, Linux and macOS are following tomorrow with /opt/Qt and ~/Qt.

I cherry-picked the two revisions into the beta branch.

I made the minimum required versions of compilers and Qt more consistent in our CMake scripts as well as the documentation.

I enhanced our CMake script to pre-set the Visual Studio redistributable, which already comes along with Visual Studio 2017.