see also T19711
Pushed new branch T25534-removeWarningsNoErrorsModules.
Pushed new branch T24987-mitkFunctionAddLibrarySearchPaths.
Discussed it. For now we will implement an simple solution (simelar to the legacy modulconf pattern) to add additional path from the eps cmakeexternals script.
This is hard to code, because the interaction with MITK can go though 2 independent systems. One that goes though the State Machines with the mitkDisplayInteractor and the other that goes through the QmitkDataManagerView. Both systems work with different resources, so linking functions from one to the other needs a bigger though process
Pushed new branch T24669-V3ExtendMatchpointWrapping.
Wed, Oct 17
Currently not merged - other plugins may need such a specific call, too
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.
Tue, Oct 16
The single-step increase/decrease feature is in the beta branch now. I'll create subtasks for remaining TODOs.
Mon, Oct 15
Pushed new branch T25522-FiducialBased-CT-to-US-registration.
Sat, Oct 13
Pushed new branch T25494-InstallerCleanup-not-for-master.
Fri, Oct 12
By the way: Linking works fine if OpenIGTLink is built separately and specified in CMake via EXTERNAL_OpenIGTLink_DIR. But the link libraries property is also empty in this case.
We figured out that the exported target OpenIGTLink does not have any linked libraries. Thank you @kislinsk for your help!
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.
LevelWindow::SetAuto is the function that crops the outliers and sets the range to the 2nd minimum / maximum value. This leads to cropping of label values for the given nifti labelmap images (this is the reason why the level window slider is set to [1,2] using the test data from above).
fixed, issue was mismatching measurement units and possibly some traces of a gibbs phenomenon for box-like bandpass window functions
I'll make an internal survey to find out in which configurations they are problems and in which Boost builds fine.
There is a problem with this approach since it might happen that a user sets it's own level window and then chooses a colormap. But this colormap will then reset the level window to the whole grey value range.