[Paraview] /usr/bin/paraview not packaged with CPack in Paraview 4.3.1 Superbuild

[Anthony Crognale]

Ben,

After removing libpng 1.6.18 from my system (which I did AFTER doing a fresh recompile of paraview), I get the following message:

/usr/lib/paraview-4.3/paraview: error while loading shared libraries: libpng16.so.16: cannot open shared object file: No such file or directory

Which seems to indicate the build system linked against the system libpng even though USE_SYSTEM_png is set to off?

Thanks,
Anthony
________________________________________
From: Ben Boeckel <ben.boeckel at kitware.com>
Sent: Monday, September 14, 2015 11:29 AM
To: Anthony Crognale
Cc: paraview at paraview.org
Subject: Re: [Paraview] /usr/bin/paraview not packaged with CPack in Paraview 4.3.1 Superbuild

On Mon, Sep 14, 2015 at 14:15:26 +0000, Anthony Crognale wrote:
> I had been using the system libpng version 1.2.52, but it appears
> `png_set_longjmp_fn` was not introduced until 1.6, so I tried building
> libpng 1.6.18 from source last night, which then allows Paraview to
> continue building with qt enabled, however, when running the built
> version, I get:
>
> libpng warning: Application built with libpng-1.4.8 but running with
> 1.6.18
>
> So it appears that there is some other version of libpng (maybe
> bundled in the superbuild?) that it was using to build.

Yeah, it looks like it built against the superbuild's libpng and running
against the one you grabbed. Other than a compiler and things like libc
or OpenGL, the superbuild *should* be providing everything it needs (and
it is not regularly tested against other external dependency versions).

> Should I turn off use_system_png? Turn off ENABLE_png? Something else?

Using the superbuild-provided png would probably be best
(-DUSE_SYSTEM_png=OFF -DENABLE_png=ON). However, it seems that removing
the 1.6.18 libpng should fix the warning.

--Ben