Missing header files

ParaView Support
1

I am trying to build ParaView with Catalyst and Python enabled. My compilation is successful, but an application that includes some ParaView header files gets stuck because some expected files are not found. For example, the files in Clients/PythonCatalyst include a file called vtkPVPythonCatalystModule.h which is not found. I am guessing that this file is not being generated due to an error in my CMake parameters, but I can’t see what is missing. Any ideas or do you know where this file should be coming from?

Thanks,
Ed

2

A few clarifying questions:

  • Are you adding -I flags manually, using CMake, or paraview-config? (the last two should handle this already)
  • Did you install ParaView or using its build tree? (if the latter, it lives in the build tree, not the source tree)

Note that ParaView would not build if that file were not there (it contains the _EXPORT symbols used to tell the compiler what classes should be accessible from the library)

3

Hi Ben,

Thank you for your reply. I am building from the ParaView-v5.10.1.tar.gz tarball using gcc 9.3.0 with the CMake command:

cmake
-DCMAKE_INSTALL_PREFIX:PATH=${INSTALL}
-DCMAKE_BUILD_TYPE=Release
-DPARAVIEW_USE_QT:BOOL=OFF
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON
$SRC_DIR

My goal is to link with SENSEI which wants Catalyst and Catalyst Python scripts. I get to a point in the SENSEI build where I see

In file included from /xyz/ParaView-v5.10.1/Clients/PythonCatalyst/vtkCPPythonScriptPipeline.h:18,
from /abc/SENSEI-4.1.0/sensei/CatalystAnalysisAdaptor.cxx:42:
/xyz/ParaView-v5.10.1/Clients/PythonCatalyst/vtkCPPythonPipeline.h:19:10: fatal error: vtkPVPythonCatalystModule.h: No such file or directory
19 | #include “vtkPVPythonCatalystModule.h” // For windows import/export of shared libraries
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

Sure enough, there is no vtkPVPythonCatalystModule.h to be found anywhere. I figure I must be doing something wrong that is preventing that file from being generated.

Ed

4

It’s not really clear why this is happening. It could just be a 5.10 thing, but I don’t think anything has changed near here in the module system since then. Is the PythonCatalyst library in the build/install tree?

5

Hello Ben,

I discovered that the problem is that I didn’t set the CMake variable PARAVIEW_USE_PYTHON. Apparently that is the trigger for generating vtkPVPythonCatalystModule.h. Thank you for checking into this problem for me.

Ed