I just tried this on my Debian machine and the biggest executable in my bin dir weighs in at 2.5 MB. Note that this is a Debug build as my Release build tree is a bit out of date at the moment. Also all of the CMake files appear to be in ParaView-3.7.0-Linux-x86_64/lib/paraview-3.7/CMake/ and all of the vtk libs are in in ParaView-3.7.0-Linux-x86_64/lib/paraview-3.7/. So this is really puzzling. Have you tried doing this from a fresh clean build? <br>
<br><div class="gmail_quote">On Fri, Mar 12, 2010 at 12:15 PM, Mark Olesen <span dir="ltr"><<a href="mailto:Mark.Olesen@faurecia.com">Mark.Olesen@faurecia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Fri, 2010-03-12 at 09:57 -0500, Utkarsh Ayachit wrote:<br>
> I haven't really read the full thread but I saw that everyone seems<br>
> to using "make install". A couple of comments about that.<br>
><br>
> Currently, we recommend users to use "cpack" to create the package<br>
> (tgz or what have you) instead of "make install" since currently,<br>
> "make install" doesn't support component-based install i.e. ParaView<br>
> source cannot pick which "INSTALL" command have any effect based on<br>
> their "COMPONENT". Consequently, you might end up with more stuff in<br>
> your install tree than expected.<br>
><br>
> To run cpack on ParaView application, you do something as follows:<br>
><br>
> cpack -G TGZ --config<br>
> <path-to-paraview-build-dir>/Applications/ParaView/CPackParaViewConfig.cmake<br>
<br>
<br>
</div>Even after having previously built everything (make && make<br>
HTMLDocumentation, as well as make preinstall for good measure) the<br>
above mentioned cpack command still takes about 5minutes to compile<br>
stuff and pack everything up.<br>
<br>
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>
<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>
<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>
I'm obviously doing something wrong - could someone please supply a<br>
recipe for doing this?<br>
<font color="#888888"><br>
<br>
/mark<br>
</font><div><div></div><div class="h5"><br>
<br>
DISCLAIMER:<br>
This electronic transmission (and any attachments thereto) is intended solely for the use of the addressee(s). It may contain confidential or legally privileged information. If you are not the intended recipient of this message, you must delete it immediately and notify the sender. Any unauthorized use or disclosure of this message is strictly prohibited. Faurecia does not guarantee the integrity of this transmission and shall therefore never be liable if the message is altered or falsified nor for any virus, interception or damage to your system.<br>
<br>
</div></div></blockquote></div><br>