Update minimum required version of CMake to 3.9.5. See this topic for more details.
Important remarks
waiting we transition Linux build from Ubuntu 10.04 VM running on factory-south.kitware to docker or VM based build running on metroplex.kitware dashboard, we will keep linux build with Qt4 and VTK7. This will happen later.
Very Exciting! You may want to speak with Matt McCormick regarding minimum OSX versions. He just completed an investigation into this regarding ITK and python.
Python 3 migration is planned, too. As far as I know, most or all Slicer dependencies support Python 3 already, so the switch could probably happen later this year, once Slicer is stabilized after VTK, Qt, and compiler updates.
To complement @lassoan answer, during the past few years we worked hard to update VTK and ITK to work nicely with Python 3. Now that PythonQt also support it. The remaining part will be to update CTK and Slicer to work with Python 3.
If this is something important for your project and you have resources to allocate for this, do not hesitate to reach out to me.
Windows build machine (named overload) has been updated two days ago but Slicer build failed because the dashboard script wasn’t setting Qt5_DIR. This was fixed yesterday in Slicer/DashboardScripts@3d50b85.
Since Qt 5.10.0 addresses issues (especially with WebEngine), I think we should go with it for the current release cycle. We could then revisit after Slicer 5.0 is out.
Starting today, Slicer packages for macOS will be done on factory-south.kitware using Qt5 and VTK9 with OpenGL2 enabled.
Deployment target will be 10.9, this means Slicer nightly package will NOT run on older operating system.
qt-easy-build scripts for macOS and Linux have been updated to support building Qt 5.10.0 without rpath. (Corresponding CircleCI and TravisCI are green)
windows:
today’s Windows packages have successfully been built using VS2015, VTK9, Qt5 and C++11
This is required to work well with the current implementation of the packaging system.
The good news is that @ihnorton is working on creating a python script that will greatly speed up the packaging process and also allow repackaging of Qt libraries installed using official installer.
Was the build of Slicer against Qt 5.10.0 and VTK9 tested on macOS ?
During the past year, a lot of people contributed to testing and stabilizing the build.
Last night, new dashboard scripts were added to support building on factory-south-macos:
Build of the Slicer application was manually started (with packaging disabled), it failed with an error related to Swig installation that should be fixed in r26877
Later today, the build was manually restarted and it completed. Packaging is now in progress, and I think it will succeed. If not, that will give us the opportunity to fix problem before the nightly start.
When I try opening from the console I get this message that indicates it’s not finding the platform library in spite of it being installed by r26882. Odd that it says it can’t find “cocoa” but also says that “cocoa” is available. Is it maybe the wrong version of the platform library file?
$ /Volumes/Slicer-4.9.0-2018-01-28-macosx-amd64/Slicer.app/Contents/MacOS/Slicer
This application failed to start because it could not find or load the Qt platform plugin "cocoa"
in "".
Available platform plugins are: cocoa.
Reinstalling the application may fix this problem.
Abort trap: 6
