<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hello again,</p>
<p><br>
</p>
<p>I'm (finally) trying to get Catalyst to successfully link to our application code on Excalibur (Cray, ARL HPC). I was able to build paraview and all of the dependencies thanks to help I've gotten on the list here in the past. However, when I try to link
my code to it (and this is a code that works fine with Catalyst on other platforms), I get:</p>
<p><br>
</p>
<p></p>
<div> CMake Error at /p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/vtkModuleAPI.cmake:120 (message):<br>
Requested modules not available:<br>
<br>
vtkPVPythonCatalyst<br>
Call Stack (most recent call first):<br>
/p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/VTKConfig.cmake:80 (vtk_module_config)<br>
/p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4/ParaViewConfig.cmake:49 (include)<br>
CMakeLists.txt:218 (find_package)<br>
<br>
The section in my CMakeLists that looks for paraview is:<br>
<br>
<div>option(LESLIE_USE_COPROCESSING "Turn on CoProcessing with Paraview" OFF)<br>
if(LESLIE_USE_COPROCESSING)<br>
find_package(ParaView REQUIRED vtkPVPythonCatalyst<br>
HINTS $ENV{PARAVIEW_CP_ROOT})<br>
include(${PARAVIEW_USE_FILE})<br>
include_directories(${PROJECT_SOURCE_DIR}/utils)<br>
add_definitions(-DPARAVIEW_COPROCESSING)<br>
endif()<br>
mark_as_advanced(LESLIE_USE_COPROCESSING)<br>
</div>
<br>
</div>
and it doesn't seem to work. On other machines, I never needed to set the PARAVIEW_CP_ROOT variable, it always just found it. When I build my code, I point the paraview directory (where it finds the paraviewConfig.cmake file) to:
<p></p>
<p><br>
</p>
<p><span>/p/home/tgallagh/pv-test/4.4.0_osmesa/lib/cmake/paraview-4.4</span></p>
<p><br>
</p>
<p>and it seems to find it okay. <br>
</p>
<p><br>
</p>
<p>Lastly, the vtkPVPythonCatalyst.so library is in the lib/paraview-4.4/site-packages/vtk directory and there is libvtkPVPythonCatalyst-pv4.4.so* and libvtkPVPythonCatalystPython27D-pv4.4.so* in lib/paraview-4.4/<br>
</p>
<p><br>
</p>
<p>I'm at a loss to understand why it is reporting the module is missing -- did I miss something somewhere?
<br>
</p>
<p><br>
</p>
<p>Thanks as always,</p>
<p><br>
</p>
<p>Tim<br>
</p>
</div>
</body>
</html>