It handles installation, but the “default” is for Unix-style installation layouts. Wheels are not compatible with them, so they need other support. If you want to see what VTK does, you can look at
CMake/vtkWheel*.cmake files in the VTK source tree. Note that such a build is only really useful for then packaging into a wheel not for use as an SDK or anything like that.
Packaging up into a wheel is not easy. VTK basically does a completely different build layout to make wheels work (because the state of Python packaging is…not great for projects with any non-Python code involved). None of the wheel auditors or whatever will like it either since you’ll need to ship all of the VTK libraries to make it happy (and
delocate just doesn’t work with
@loader_path, so you need to setup rpaths manually). @jcfr has ideas on how VTK-using wheels can be done, but it all sounds very hacky and “if it works, great; if not, go ask for better Python packaging support of non-Python code” to me.