yamato link-collisions # ls /usr/lib/paraview-3.3/libvtk* /usr/lib/paraview-3.3/libvtkClientServer.so /usr/lib/paraview-3.3/libvtkPVServerCommonPython.so /usr/lib/paraview-3.3/libvtkCommon.so /usr/lib/paraview-3.3/libvtkPVServerCommonPythonD.so /usr/lib/paraview-3.3/libvtkCommon.so.pv3.3 /usr/lib/paraview-3.3/libvtkPVServerManager.so /usr/lib/paraview-3.3/libvtkCommonCS.so /usr/lib/paraview-3.3/libvtkPVServerManagerPython.so /usr/lib/paraview-3.3/libvtkCommonPython.so /usr/lib/paraview-3.3/libvtkPVServerManagerPythonD.so /usr/lib/paraview-3.3/libvtkCommonPythonD.so /usr/lib/paraview-3.3/libvtkParallel.so /usr/lib/paraview-3.3/libvtkDICOMParser.so /usr/lib/paraview-3.3/libvtkParallel.so.pv3.3 /usr/lib/paraview-3.3/libvtkDICOMParser.so.pv3.3 /usr/lib/paraview-3.3/libvtkParallelCS.so /usr/lib/paraview-3.3/libvtkFiltering.so /usr/lib/paraview-3.3/libvtkRendering.so /usr/lib/paraview-3.3/libvtkFiltering.so.pv3.3 /usr/lib/paraview-3.3/libvtkRendering.so.pv3.3 /usr/lib/paraview-3.3/libvtkFilteringCS.so /usr/lib/paraview-3.3/libvtkRenderingCS.so /usr/lib/paraview-3.3/libvtkGenericFiltering.so /usr/lib/paraview-3.3/libvtkViews.so /usr/lib/paraview-3.3/libvtkGenericFiltering.so.pv3.3 /usr/lib/paraview-3.3/libvtkViews.so.pv3.3 /usr/lib/paraview-3.3/libvtkGenericFilteringCS.so /usr/lib/paraview-3.3/libvtkViewsCS.so /usr/lib/paraview-3.3/libvtkGraphics.so /usr/lib/paraview-3.3/libvtkVolumeRendering.so /usr/lib/paraview-3.3/libvtkGraphics.so.pv3.3 /usr/lib/paraview-3.3/libvtkVolumeRendering.so.pv3.3 /usr/lib/paraview-3.3/libvtkGraphicsCS.so /usr/lib/paraview-3.3/libvtkVolumeRenderingCS.so /usr/lib/paraview-3.3/libvtkHybrid.so /usr/lib/paraview-3.3/libvtkWidgets.so /usr/lib/paraview-3.3/libvtkHybrid.so.pv3.3 /usr/lib/paraview-3.3/libvtkWidgets.so.pv3.3 /usr/lib/paraview-3.3/libvtkHybridCS.so /usr/lib/paraview-3.3/libvtkWidgetsCS.so /usr/lib/paraview-3.3/libvtkIO.so /usr/lib/paraview-3.3/libvtkXdmf.so /usr/lib/paraview-3.3/libvtkIO.so.pv3.3 /usr/lib/paraview-3.3/libvtkXdmfCS.so /usr/lib/paraview-3.3/libvtkIOCS.so /usr/lib/paraview-3.3/libvtkexoIIc.so /usr/lib/paraview-3.3/libvtkImaging.so /usr/lib/paraview-3.3/libvtkexoIIc.so.pv3.3 /usr/lib/paraview-3.3/libvtkImaging.so.pv3.3 /usr/lib/paraview-3.3/libvtkftgl.so /usr/lib/paraview-3.3/libvtkImagingCS.so /usr/lib/paraview-3.3/libvtkftgl.so.pv3.3 /usr/lib/paraview-3.3/libvtkInfovis.so /usr/lib/paraview-3.3/libvtkhdf5.so /usr/lib/paraview-3.3/libvtkInfovis.so.pv3.3 /usr/lib/paraview-3.3/libvtkmetaio.so /usr/lib/paraview-3.3/libvtkInfovisCS.so /usr/lib/paraview-3.3/libvtkmetaio.so.pv3.3 /usr/lib/paraview-3.3/libvtkNetCDF.so /usr/lib/paraview-3.3/libvtksqlite.so /usr/lib/paraview-3.3/libvtkNetCDF.so.pv3.3 /usr/lib/paraview-3.3/libvtksqlite.so.pv3.3 /usr/lib/paraview-3.3/libvtkPVCommandOptions.so /usr/lib/paraview-3.3/libvtksys.so /usr/lib/paraview-3.3/libvtkPVFilters.so /usr/lib/paraview-3.3/libvtksys.so.pv3.3 /usr/lib/paraview-3.3/libvtkPVFiltersCS.so /usr/lib/paraview-3.3/libvtkverdict.so /usr/lib/paraview-3.3/libvtkPVPythonInterpretor.so /usr/lib/paraview-3.3/libvtkverdict.so.1.2 /usr/lib/paraview-3.3/libvtkPVServerCommon.so /usr/lib/paraview-3.3/libvtkverdict.so.1.2.0 /usr/lib/paraview-3.3/libvtkPVServerCommonCS.so
I think this is non-trivial: http://www.paraview.org/pipermail/paraview/2008-June/008194.html Would be very cool though!
Very non-trivial indeed :) However, if somebody has any pointers of how this could be achieved please let me know. cheers, Markus
With the current version ParaView-3.98.1 it appears impossible to fix as the internal bundled VTK appears to be some unknown pre-release version internally labelled as 6.0.0, while as the latest available vtk release is 5.10.1. % cat ParaView-3.98.1-source/VTK/CMake/vtkVersion.cmake # VTK version number components. set(VTK_MAJOR_VERSION 6) set(VTK_MINOR_VERSION 0) set(VTK_BUILD_VERSION 0) %
Paraview and VTK are one upstream and I don't expect them to have no good reason for bundling. In fact, they use TWO repositories. One for the vanilla VTK and one vor ParaviewVTK, check: http://paraview.org/gitweb?p=PVVTK.git http://vtk.org/gitweb?p=VTK.git If there are any bugs, security issues etc they fix them in both repositories anyway. so this bug will either be left open forever or get closed as wontfix
I checked a few days ago... both repos seem 100% the same. But I guess it will be a major pain to unf*ck the build system so that it picks the system vtk. And actually... not very high priority to me, since it's the same upstream.
*** Bug 505872 has been marked as a duplicate of this bug. ***
The overcomplex CMake build system, that paraview uses, would have to be rewritten almost entirely in order to support an external vtk copy. :-/
We will not fix that in the foreseeable future. :-(
It looks like PARAVIEW_USE_EXTERNAL_VTK exists now?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4342b5087bd84cbe64de318c152b5425ec7f8d7b commit 4342b5087bd84cbe64de318c152b5425ec7f8d7b Author: Sam James <sam@gentoo.org> AuthorDate: 2021-06-02 01:23:23 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-06-02 01:23:23 +0000 sci-libs/vtk: delete README from bundled vtkm for now Avoids collision with paraview. We'll ideally try to get paraview building with system VTK again but VTK takes a while to build so anything to prevent collisions for users now is important while we investigate that possibility. Bug: https://bugs.gentoo.org/253881 Bug: https://bugs.gentoo.org/793221 Signed-off-by: Sam James <sam@gentoo.org> sci-libs/vtk/vtk-9.0.1.ebuild | 5 +++++ 1 file changed, 5 insertions(+)
I was working on testing paraview against an external vtk-9 and found this in ParaViewOptions.cmake: # XXX(VTK): External VTK is not yet actually supported. if (FALSE) option(PARAVIEW_USE_EXTERNAL_VTK "Use an external VTK." OFF) mark_as_advanced(PARAVIEW_USE_EXTERNAL_VTK) else () set(PARAVIEW_USE_EXTERNAL_VTK OFF) endif () So it seems, like we have to live for now with the hack from comment #10