I get the error that superbuild can’t find Python3. This especially confuses me since I don’t use the system-provided python. I would expect superbuild to fetch is automatically.
Here are my cmake options:
And here is the error:
CMake Error at /shared/opt/cmake-3.14.2-Linux-x86_64/share/cmake-3.14/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find Python3 (missing: Python3_EXECUTABLE Interpreter)
Call Stack (most recent call first):
Why not trying with 5.6.0 ?
That’s just the binary I happen to have downloaded on my laptop a while ago. Why not RC2?
Because it is not a release. Please try with the latest release, 5.6.0.
The superbuild doesn’t support Python3 at the moment (building it or consuming it), sorry. It’s on the plan for the next spring release at the latest.
Thanks @ben.boeckel and @mwestphal. So, when I try to build 5.6.0 now, I get this ospray error:
CMake Error at VTK/Rendering/RayTracing/CMakeLists.txt:52 (find_package):
Could not find a configuration file for package "ospray" that is compatible
with requested version "1.8".
The following configuration files were considered but not accepted:
/shared/opt/parabuild/install/lib/cmake/ospray-1.6.1/osprayConfig.cmake, version: 1.6.1
Shouldn’t superbuild be grabbing the right ospray version? Or is there a cmake flag I’m missing? I only used -DENABLE_ospray=ON and -Dospray_SOURCE_SELECTION:STRING=for-git .
Did you choose the 5.6.0 selection for ParaView? It’s best to use the
v5.6.0-1 superbuild tag rather than
master. For various reasons,
master can drift and move ahead of what older ParaView sources expect.
Yeah, apparently. When I tried not using ospray, I instead got this error:
sed: can’t read /shared/opt/parabuild/install/lib/cmake/paraview-5.6/Modules/vtkCommonCore.cmake: No such file or directory
CMake Error at /shared/opt/paraview-superbuild/projects/scripts/paraview.fixupcmakepaths.cmake:39 (message):
Failed to patch
I’ll let you know if the tag you suggested does the trick. Thanks so much!
I’ll note that the readme mentions this: https://gitlab.kitware.com/paraview/paraview-superbuild/#building-a-specific-version. Is there someplace we should put it to be more prominent? Or maybe we should be more proactive in removing release selections once we’re pretty sure they’re not going to work for “common” cases?
Oh, I am at fault for not reading into that more. Unfortunately, I just skimmed and expected it to work. Thanks for pointing that out.