[Paraview] Building standalone vtk within Paraview

[Ken Martin]

What we typically do here at Kitware is have one source tree and then two
binary trees. One binary tree is for ParaView and the other ParaView tree is
for VTK. We point the VTK binary tree to the VTK subdirectory in the
ParaView source tree. That way we can make changes to the source tree and
test both ParaView and VTK. Of course this requires building both VTK and PV
which ends up duplicating a bunch of .o files but it's not too bad.

Ken


> When building paraview, only a subset of the vtk is wrapped in tcl,
> which means that for testing regular vtk code with tcl, one must build
> vtk on its own, and also build paraview separately.
> 
> I'd like to build Paraview alone, and have it produce a complete vtk
> build so that one set of libraries and one set of build can be done to
> cover both.
> Having looked at the cmakelists files I see that VTK_WRAP_TCL is forced
> to false, and then a separate Utilities/VTKTclWrapping set of stuff is
> invoked.
> 
> By disabling the forcing of VTK_WRAP_TCL and clearing one of the COPY
> Tcl/tk lib flags, I was able to produce most of the tcl wrappers, but
> the xdmf utility died on VTK_WRAP_TCL2 command.
> 
> Can anyone briefly outline how I would do this cleanly within Paraview.
> It'd be nice to have a
> BUILD_VTK_COMPLETE flag which could be enabled and would result in a
> full set of vtk libs being produced.
> 
> Any reason why this can't be accomplished (subject to those flags which
> Paraview needs to force).
> 
> thanks
> 
> JB
> 
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview