Yes and Yes.<br><br><div class="gmail_quote">On Fri, Mar 12, 2010 at 1:22 PM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> The resulting tar.gz file may look fairly clean, but all of the cmake<br>
> files are missing (which means it can't be used for building plugins).<br>
> I thought that the cpack was supposed to pick up what was specified to<br>
> cmake, but it didn't seem to know that<br>
> PARAVIEW_INSTALL_DEVELOPMENT:BOOL=ON had been specified ... and it still<br>
> can't find its documentation.<br>
<br>
</div>Dave, can you verify this?<br>
<div class="im"><br>
<br>
> Another interesting result (I really didn't expect this):<br>
> All of the VTK libraries have been eliminated and instead the bin/<br>
> directory contains monster binaries: paraview, pvdataserver,<br>
> pvrenderserver, pvserver with about 162M-177MB each.<br>
<br>
</div>Are you building static libraries? Make sure BUILD_SHARED_LIBS is ON<br>
and VTK_USE_RPATH is OFF.<br>
<div class="im"><br>
<br>
> I don't mean to be particular obtuse, but how in the world does one<br>
> manage achieve the following:<br>
> A working paraview<br>
> - that is fully relocatable<br>
> - that can be used for building plugins<br>
> - that also manages to find its own documentation.<br>
<br>
</div>Dave, can we add a set of instructions on the Wiki detailing every<br>
step to follow (all cmake variables etc) for this?<br>
<font color="#888888"><br>
Utkarsh<br>
</font></blockquote></div><br>