VTK 9 uses different CMake options for modules than VTK 8

Kitware / fletch

Computer Vision Software Development Environment

63 stars 54 forks source link

VTK 9 uses different CMake options for modules than VTK 8 #647

Closed mleotta closed 3 years ago

mleotta commented 3 years ago

The CMake options for enabling modules have changed in VTK 9, so setting the old options was no longer enabling Qt support in VTK 9. Note that QtWebKit is not longer a sub-option, so we can just turn the whole Qt group on.

mleotta commented 3 years ago

Centos seems to have unrelated test failures. This PR should not change anything for builds unless they are configured to use VTK 9, which is currently not the default.

dstoup commented 3 years ago

VTK turns on automatically for kwiver if it's found. I think you're probably right though. I replicated the CI run on that machine and everything passed. Merging.