[Paraview] Development Install Tree

[Dave Partyka]

Hi Mark,

vtkWrapClientServer should be installed now correctly in the bin dir.
Apparently there was a bug in the install rule that installed it. Thanks for
catching that!

Committer: Dave Partyka <dave.partyka at kitware.com>
/cvsroot/ParaView3/ParaView3/Utilities/VTKClientServer/Wrapping/CMakeLists.txt,v
 <--  Utilities/VTKClientServer/Wrapping/CMakeLists.txt

new revision: 1.12; previous revision: 1.11

On Mon, Mar 15, 2010 at 6:08 AM, Mark Olesen <Mark.Olesen at faurecia.com>wrote:

> On Fri, 2010-03-12 at 13:11 -0500, Dave Partyka wrote:
> > 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?
>
> I just tried it again (from a fresh build directory and with
> GENERATE_FILTERS_DOCUMENTATION:BOOL=ON instead of "make
> HTMLDocumentation") and it looks a fair bit better. I suspect my
> previous problems might have been from mixing build and install
> directories.
>
> Using cpack, I no long have monster binaries, just that the VPIC lib
> seems to have gone missing:
>
>    paraview-real: error while loading shared libraries: libVPIC.so:
>    cannot open shared object file: No such file or directory
>
> ... but it is also getting missed for the "make install" target too, so
> the problem is elsewhere. As a stop-gap, sync'ing the library from the
> build directory did the trick.
>
>
> Apart from the inconvenience of using cpack (I really just want to
> create an installed version and not a tar.gz that I have to subsequently
> unpack and rename the directories to suit my own conventions), I'm a
> disconcerted by that fact that the cpack variant also seems to miss
> installing a fair number of files (see attached diff from ls -1R
> outputs).
>
> Apart from various missing headers, the resulting cpack'ed installation
> doesn't work for building plugins later on since it is missing
> vtkWrapClientServer.
>
> make[2]: *** No rule to make target
> `paraview-3.7.0/bin/vtkWrapClientServer', needed by ...
>
>
> The installation with "make install" did work though.
>
>
> This seems to be the current status:
> - use separate build and install directories!
> - use "make install" -- cpack misses too many files and is too clumsy
> for a local install.
> - GENERATE_FILTERS_DOCUMENTATION should work, but doesn't.
> - "make HTMLDocumentation" doesn't seem to work either
>
>
> These tests were made against this commit level:
>
> commit a75e52603fe6c70b36a6a6523f962fc598919a63
> Author: KWSys Robot <kwrobot at kitware.com>
> Date:   Fri Mar 12 05:01:10 2010 +0000
>
>    KWSys Nightly Date Stamp
>
>
>
>
> /mark
>
>
> DISCLAIMER:
> 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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20100316/5ee3c704/attachment-0001.htm>