VTK 9.2.6 brings OSMesa wheel variants #4024
banesullivan
announced in
Announcements
Replies: 2 comments
-
I also want to point any adventurous/brave developers to these CMake configurations if hoping to build OSMesa, EGL, or other build "variants" for other platforms: https://github.com/banesullivan/vtk-cmake These configurations generally match the configurations used by VTK to publish the PyPI wheel |
Beta Was this translation helpful? Give feedback.
0 replies
-
FYI, another status update: https://discourse.vtk.org/t/status-update-vtk-python-wheels/11212 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
With VTK 9.2.6, Kitware is now shipping an OSMesa wheel variant for manylinux: https://gitlab.kitware.com/vtk/vtk/-/packages/102
This is installable as (ignore the personal access token stuff on GitLab):
To distinguish these wheel variants, the distribution name is
vtk-osmesa
, which does not match thevtk
in PyVista's core dependencies. Care must be take to make sure you do not have bothvtk-osmesa
andvtk
in the same environment. A simple, yet not pretty approach is to install PyVista, uninstallvtk
, then install the OSMesa variant:Hopefully a future version of setuptools will make it easier for PyVista to specify different default installation requirements to streamline the installation of this OSMesa variant: pypa/setuptools#1139
Why is this useful
No more virtual framebuffers and no more apt installing! Goodbye
xvfb
!The
vtk-osmesa
wheel bundles all the needed dependencies and is specifically for off-screen rendering. This wheel is optimal for managed, deployed environments like we often see on platforms like MyBinder, Heroku, Google Colab, SageMaker, etc.Simply
pip install
this wheel for your JupyterLab environment and start using PyVista!Further, this will make CI testing quite a bit easier for downstream projects
Beta Was this translation helpful? Give feedback.
All reactions