Source: facet-analyser Followup-For: Bug #1040334 Looking at the upstream repo, upstream is indeed using paraview to build, not released VTK. i.e. it uses paraview's version of VTK
https://github.com/romangrothausmann/FacetAnalyser : -DVTK_DIR=/paraview-build-dir/VTK/ see also https://github.com/romangrothausmann/FacetAnalyser/blob/5d756e0fe188ecdabfe319eaebc5369eb86aa451/Dockerfile#L95 https://github.com/romangrothausmann/FacetAnalyser/issues/1#issuecomment-536537740 Somewhat little worse still, upstream keeps their own VTK https://github.com/romangrothausmann/FacetAnalyser/blob/5d756e0fe188ecdabfe319eaebc5369eb86aa451/Dockerfile#L45 but I gather it's the VTK compatible with paraview, not VTK release. Then as far as the conflict with ITK (and hence VTK) goes, upstream is building their own ITK, https://github.com/romangrothausmann/FacetAnalyser/blob/5d756e0fe188ecdabfe319eaebc5369eb86aa451/Dockerfile#L66 so their ITK is built against their (paraview-compatible) VTK, not using VTK release. So, it's still a mess.
