VTK-vtk-module-find-packages.cmake fails to find Boost

In Situ Support
21

>> ParaView_INCLUDE_DIR isn’t necessary
anymore. Instead, just link to ParaView::Catalyst

`I am missing something. I need````ParaView_INCLUDE_DIR at compile time.I have files which e.g. “#include
<vtkNonOverlappingAMR.h>”. How can I compile my code
without```ParaView_INCLUDE_DIR?``

`` On another topic, at link time I hit issues I do not
have when link to a Catalyst build. I get ’ undefined
reference to `_PyUnicodeUCS2…’. I wonder if it relates
to the system python, or I am missing a PYTHONPATH ?
Paraview-config.cmake doesn’t
set PARAVIEW_PYTHONPATH,

– PARAVIEW_ENABLE_PYTHON= ON

      -- PARAVIEW_PYTHONPATH   =
  ``````

and paraview CMakeCache.txt is correct:

      Python2_EXECUTABLE

/ascldap/users/tesari/local/python-2.7.16/bin/python2.7

      Python2_INCLUDE_DIR

/ascldap/users/tesari/local/python-2.7.16/include/python2.7

      Python2_LIBRARY_RELEASE

/ascldap/users/tesari/local/python-2.7.16/lib/libpython2.7.so

Could you advise, please?

    .../build/lib64/libvtkWrappingPythonCore-pv5.6.so.1:

undefined reference to `_PyUnicodeUCS2_AsDefaultEncodedString’

    .../build/lib64/libvtkPVCinemaReader-pv5.6.so.1: undefined

reference to `PyUnicodeUCS2_AsLatin1String’

22

I figured out why I got “undefined reference to
`_PyUnicodeUCS2_AsDefaultEncodedString’”. The reason was
that RPATH in the shared objects listed
both, the build path and the install path. Linker
issued warnings of ‘circular dependencies’, and that not all
shared objects may be resolved correctly (don’t have the exact
screenshot). In order to brake the circular dependencies I set CMAKE_SKIP_RPATH=ON ,
but the build path was still listed in
RPATH. I had to set both, CMAKE_SKIP_INSTALL_RPATH=OFF
and CMAKE_SKIP_RPATH=OFF
, and to set LD_LIBRARY_PATH
,to make it work. Is this the right way to install a
paraview build?

23

I am missing something. I need ParaView_INCLUDE_DIR

You’re missing target_link_libraries(yourtgt PRIVATE VTK::CommonDataModel) (could also be PUBLIC depending on how you’re using it) for that header.

UCS2 problems

It seems to me that ParaView was built against a UCS2 Python build, but is finding a UCS4 Python build when you’re linking to ParaView.