[vtk-developers] vtk-8.2.0-rc2 problem building wheels

[Ben Boeckel]

On Fri, Dec 07, 2018 at 17:00:20 -0500, Jean-Christophe Fillion-Robin wrote:
> > distribution builds should try to enable *everything*
> 
> In that context, I don't think it makes sense to build VTK own python
> interpreter. Ideally, it should be possible to run VTK test with or without
> it.

Yes, it is very odd that we've always built our own interpreter. IMO,
it'd be better to just set PYTHONPATH on the test suite and use a
standard Python executable.

> I also envision we could have a "vtk-openvr" python module but it wouldn't
> be available by default when installing vtk wheel. To support this level of
> "modularity" , we would continue building part of VTK independently (for
> example, we can already do this with the VTKOpenVR module)

The new module system doesn't support this at the moment (i.e., the
`find_package(VTK)` code has been ripped out of the OpenVR module). The
problem with this is that if a module can be built inside and outside of
VTK, dependent projects cannot know whether to do `find_package(VTK
COMPONENTS RenderingOpenVR)` or `find_package(VTKOpenVR)`.

--Ben