SlicerVMTK extension not building with Slicer 4.11 on MacOS

Development
, ,
1

On CDash, the SlicerVMTK extension stopped building after Slicer and VTK changes on Oct 1. All platforms are affected: http://slicer.cdash.org/index.php?project=SlicerPreview&date=2018-11-05&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=VMTK

On Oct 1 and earlier, there were packaging problems with macOS: http://slicer.cdash.org/index.php?project=SlicerPreview&date=2018-10-01&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=VMTK

This error looks similar to errors reported earlier: VMTK vessel filtering not working

I have a PR in SlicerExtension-VMTK, but it doesn’t address either of these issues. I don’t understand the build well enough yet to fix these. Help?

2

I’ve fixed the build errors on Windows (probably it fixes the same issue on other platforms, too). I’ve submitted a pull request to upstream VMTK (https://github.com/vmtk/vmtk/pull/317), and until the changes are integrated, I’ve updated Slicer VMTK extension to use my fork of VMTK instead (that contains the fix).

2 Likes
3

Thank you very much for that, Andras. I’ll change my Sept4-application-superbuild-fix branch to use your VMTK fix, and try it.
Looking at CDash, your VMTK fix has resolved the recent errors. The problem with accessing the VMTK shared object libraries on MacOS is still there, unfortunately.
Thanks again!

4

In the mean time, I merged https://github.com/vmtk/SlicerExtension-VMTK/pull/15, we can revisit after upstream vmtk is updated.

5

That’s excellent, thanks @jcfr.

Do you know what may be causing the build errors on Mac?
http://slicer.cdash.org/index.php?project=SlicerPreview&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=VMTK

6

I added an issue to SlicerExtension-VMTK.