Closed hadim closed 8 years ago
The problem is that this is not an optional dependency, i.e. if you compile VTK with Qt then Qt becomes a runtime, hard dependency of VTK.
A very common misunderstanding though, as I'm starting to experience. :) I wonder if it will ever become a possibility for VTK to switch at runtime!
Sorry @ccordoba12 I am not sure to understand. Does that mean by enabling Qt during the build, Qt MUST be present during runtime ?
In this case we could build an alternative version of vtk having Qt support ? http://conda.pydata.org/docs/building/meta-yaml.html#features
Note that I was able to use from vtk.qt.QVTKRenderWindowInteractor import QVTKRenderWindowInteractor as vtk_renderer
with the vtk version in conda forge... so I guess I have everything I need here.
Should I close ?
That does sound like a valid workaround.
@jakirkham @ocefpaf the need for a policy on alternative builds (optional deps) is a recurring topic... :)
Had opened this issue ( https://github.com/conda/conda/issues/3299 ) awhile back. Not much we can do until it is solved in conda
/conda-build
.
There's are some discussions on how to address this: https://github.com/conda/conda-build/issues/1338
I guess the option needs to be enable during the build. Qt4 is available in conda forge and Qt5 should be also available soon.
See here for Qt5 progress https://github.com/conda-forge/qt-feedstock/issues/5