[Paraview-developers] build vtk based application using paraview superbuild

[Chiranjib Sur]

Hi Ken,
Thanks for your message.

I think my error was I was trying to include find_package(ParaView) and
find_package(VTK) together. Once I cleaned up and just kept the
include_package(Paraview), the error disappears. Finally I use the
following lines

find_package(ParaView )
include(${PARAVIEW_USE_FILE})

....

target_link_libraries(MyExecutable ${PARAVIEW_LIBRARIES} ${VTK_LIBRARIES} )

Thinks works perfect and my application find the required VTK packages
which comes with the PV superbuild.

Thanks,
Chiranjib

On Tue, Apr 5, 2016 at 8:06 PM, Moreland, Kenneth <kmorel at sandia.gov> wrote:

> Does the CMakeLists.txt of your VTK-based application have a command like
> find_package(ParaView)? If not, then the ParaView_DIR variable probably
> has no meaning.
>
>
>
> Do you have a command like find_package(VTK)? If so, you probably want to
> set VTK_DIR instead of ParaView_DIR.
>
>
>
> -Ken
>
>
>
>
>
> *From: *Paraview-developers <paraview-developers-bounces at paraview.org> on
> behalf of Chiranjib Sur <sur.chiranjib at gmail.com>
> *Date: *Tuesday, April 5, 2016 at 6:51 AM
> *To: *Paraview Developer Mailing list <paraview-developers at paraview.org>
> *Subject: *[EXTERNAL] [Paraview-developers] build vtk based application
> using paraview superbuild
>
>
>
> Hi,
>
> I am trying to build a stand alone VTK based application linking with
> ParaView superbuild.
>
>
>
> I ran the cmake command to create the Makefile linking with PV super build
>
> (-DParaView_DIR=/superbuild/install/location)
>
>
>
> However, I get the following warning and I could not use the libraries
> from PV
>
>
>
> CMake Warning:
>
>    Manually -specified variables were not used by the project:
>
>
>
>         ParaView_DIR
>
>
>
>
>
> Any pointer on how I should modify my CMakeLists.txt for this purpose?
>
>
>
> Thanks in advance,
>
> Chiranjib
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20160406/98be3762/attachment.html>