[Paraview] paraview and vtk
Weiguang Guan
guanw at rhpcs.mcmaster.ca
Tue Mar 1 13:16:44 EST 2005
Yes, there is a fairly large overlap. When you "make install" paraview its
own vtk will overwrite the separately built/installed vtk (if there is
one). And this might cause some vtk-based applications broken as these two
VTKs are "slightly" different versions and built with different cmake
options as Brad pointed out.
Weiguang
--
========================================================
Weiguang Guan, Research Engineer
RHPCS, McMaster University
========================================================
On Tue, 1 Mar 2005, don fisher wrote:
> Brad,
>
> When a separate VTK is built and installed, do you know whether there
> is an overlap of files in the lib and include directories? It appeared
> that there might be (even though there was a VTK subdir in lib) but I
> did not have time to verify all of the load times.
>
> don
>
> Brad King wrote:
> > Weiguang Guan wrote:
> >
> >> I'm new to paraview. Just wonder why paraview keeps its own copy of
> >> vtk. If I download/install vtk, and want to link with the separately
> >> installed vtk rather than the one that comes with paraview, is there a
> >> switch in cmake (paraview's CMakeLists.txt) that allow me to do this?
> >
> >
> > ParaView used to support an external VTK but it requires VTK to be built
> > with a specific set of options. It also requires a matching version of
> > VTK (down to the second in CVS time). We had too many problems with
> > users not having matching versios of VTK or building it with conflicting
> > options or compilers. The solution is to include VTK with ParaView to
> > make it all do the right thing automatically. It turns out that only a
> > minimal part of VTK needs to be built and that ParaView's VTK wouldn't
> > be that useful as a stand-alone VTK anyway.
> >
> > -Brad
> > _______________________________________________
> > ParaView mailing list
> > ParaView at paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview
> >
>
>
More information about the ParaView
mailing list