[Paraview] Integrating precompiled Catalyst into external projects

[Andy Bauer]

Hi Jimmy,

If you're building Catalyst and want to install for others to link against
you will want to enable the PARAVIEW_INSTALL_DEVELOPMENT_FILES CMake option
when configuring.

It may be possible to have precompiled Catalyst installs with development
files available but there hasn't been a strong call for that to be done.

Cheers,
Andy

On Wed, Jul 5, 2017 at 8:08 AM, A . <super_achie at hotmail.com> wrote:

> Dear members,
>
>
> I would like to have Catalyst precompiled and ready for use for developers
> that want to work on my project. In this way they don't need to go through
> the procedure of installing dependencies and building Catalyst themselves
> (which currently takes longer than building my project...).
>
>
> The problem is the absolute paths that are used in all the .cmake files,
> such as ParaViewConfig.cmake and UseParaView.cmake (and all .cmake files
> they call on).
>
>
> I thought a "make install" would do the trick as normally it will copy all
> the essential files (system independent) to the CMAKE_INSTALL_PREFIX
> directory. But I cannot use the contents of the installation folder as the
> directory to point to when linking to Catalyst in my project (since there
> are no configuration files copied).
>
>
> I was doubtful to ask this question, because if it were possible, I would
> expect a precompiled Catalyst to be hosted on the ParaView download page.
> But out of curiosity I ask nonetheless; is it possible?
>
>
> Best,
>
> Jimmy
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170706/a72165f1/attachment.html>