[Paraview-developers] [Paraview] Development Install Tree

[Utkarsh Ayachit]

> The resulting tar.gz file may look fairly clean, but all of the cmake
> files are missing (which means it can't be used for building plugins).
> I thought that the cpack was supposed to pick up what was specified to
> cmake, but it didn't seem to know that
> PARAVIEW_INSTALL_DEVELOPMENT:BOOL=ON had been specified ... and it still
> can't find its documentation.

Dave, can you verify this?


> Another interesting result (I really didn't expect this):
> All of the VTK libraries have been eliminated and instead the bin/
> directory contains monster binaries: paraview, pvdataserver,
> pvrenderserver, pvserver with about 162M-177MB each.

Are you building static libraries? Make sure BUILD_SHARED_LIBS is ON
and VTK_USE_RPATH is OFF.


> I don't mean to be particular obtuse, but how in the world does one
> manage achieve the following:
>  A working paraview
>  - that is fully relocatable
>  - that can be used for building plugins
>  - that also manages to find its own documentation.

Dave, can we add a set of instructions on the Wiki detailing every
step to follow (all cmake variables etc) for this?

Utkarsh