SlicerExtension-VMTK build failing on MacOS 10.12, VTKv9, Qt 5.10

Do you know which is the latest Slicer revision on which VMTK works / how I can figure it out?

You can look at the build and testing record for Slicer and extensions at http://slicer.cdash.org/viewProjects.php. Open the tools, click Show Filters, and search for the Build Name VMTK. The Slicer4 project uses Qt4.8, and there are successful builds of the VMTK extension there (the Qt5 build is SlicerPreview). The latest ones haven’t built properly because there is a pending pull request at vmtk/SlicerExtension-VMTK that someone needs to review and accept. The last successful build of the extension was on June 13:
http://slicer.cdash.org/index.php?project=Slicer4&date=2018-06-13&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=VMTK

1 Like

Here’s where I posted about VTK9 compatibility for VMTK. Feel free to add comments expressing your interest.
https://groups.google.com/forum/#!topic/vmtk-users/rhMaE8W8oi0

1 Like

I’ve submitted a pull request to the Slicer ExtensionsIndex, so that SlicerVMTK is fetched from vmtk/SlicerExtension-VMTK. At the moment, it’s still trying to fetch from a deleted branch of @jcfr’s repository, and failing. I don’t have Write permission - could someone review and accept it? Or may I have Write permission?

I’ve narrowed down what changes in VTK have led to problems compiling VMTK for SlicerPreview. The last VTK9 revision that results in a successful VMTK build was merged into master on Dec 13, 2017: c96fe3bca6bdb7df83252f8a443d8e0428cab956, “Merge branch ‘upstream-expat’ into update-expat”. The commit that follows it deals with vtkWrapHierarchy.

For two days after that, I can’t get VTK itself to compile, then with revisions from Dec 15 onwards I get the error we’ve been seeing in the recent build attempts. @jcfr, @lassoan, do you have any insight into why that change would cause problems, and how to address it? Thanks for any assistance.
I wrote more about it in the last comments here:

Hi Folks,

To follow up with this, the build system of VMTK has been fixed and a PR has been submitted, it is currently waiting to be integrated:

In the process, we also discovered an issue in conda-build which has also been fixed in the upstream project:

@mschumaker Thanks for your patience

1 Like

@jcfr Thanks so much for pursuing this! I appreciate your efforts.