Thank you so much for your message. I dowloaded the super-build and I am trying to compile it with OSMESA (llvm and mesa are already compiled in my computer). I am using the following flags:
However it crashes because python 2 or 3 have not been enabled:
-- Building projects: cxx11, nlohmannjson, python, pybind11, paraview
CMake Error at superbuild/projects/python.cmake:2 (message):
Python is enabled, but neither Python2 nor Python3 has been enabled.
Call Stack (most recent call first):
superbuild/cmake/SuperbuildMacros.cmake:983 (include)
superbuild/CMakeLists.txt:159 (superbuild_process_dependencies)
I also read the post below because some people were experiencing the same issue and you recommended using the flag " -D ENABLE_python3":
However for the current super-build version, that cmake flag is not recognized, I also tried:
There is no reason to specify such cmake options, just enable what you need and the superbuild will download and build it for you. This is literally the point of the superbuild, you do not need to build the dependencies yourself.
The reason for this is that I need to use ParaView in parallel to compute some field in a reasonable time but I noticed that I have problems when using multiple CPUs, see my previous post here to now more about the issue:
However, I ran by chance in our HPC the ParaView version with osmesa using multiple-CPUs and I didn’t have the problem so now I believe that the solution to all my issues is to use a compiled version of ParaView using osmesa since I normally do CPU-based rendering.
It works for the -DENABLE_osmesa=ON compilation but it fails when I set -DENABLE_qt5=ON. Do I need to set any additional flag to correctly compile Paraview with the GUI?
So if I understand correctly, I can source the binary files from the latest Paraview Version (nightly/Master Version from https://www.paraview.org/download/) to use the GUI and then use pvserver to connect to the built version with OSMESA right? Something like this:
I can connect to the SuperBuild server from the master version but then I have the problem regarding the readers since I haven’t compiled the version 5.11. Also I didn’t add -DPARAVIEW_ENABLE_VISITBRIDGE=ON \ during the superbuild compilation (since I thought that it would be included by default) so maybe that’s why the readers are not available in the pvserver. However adding the aforementioned flag doesn’t seem to work for the superbuild:
I manage to build the 5.10.1 tag to completion on Ubuntu 20.04 (no discrete GPU)
However, when I try to do a ninja install I get the following errors
Copying /home/nyue/projects/ParaView/superbuild/qt-build/install/lib/catalyst/libcatalyst-paraview.so ==> lib/catalyst
CMake Error at cmake_install.cmake:1478 (message):
Failed to install
/home/nyue/projects/ParaView/superbuild/qt-build/install/lib/catalyst/libcatalyst-paraview.so:
objdump:
'/home/nyue/projects/ParaView/superbuild/qt-build/install/lib/catalyst/libcatalyst-paraview.so':
No such file
Traceback (most recent call last):
File "/home/nyue/projects/ParaView/superbuild/paraview-superbuild_git/superbuild/cmake/scripts/fixup_bundle.unix.py", line 750, in <module>
main(sys.argv[1:])
File "/home/nyue/projects/ParaView/superbuild/paraview-superbuild_git/superbuild/cmake/scripts/fixup_bundle.unix.py", line 742, in main
_install_binary(main_exe, is_excluded, bundle_dest, opts.libdir, installed, manifest, opts.source, dry_run=opts.dry_run, look_for_symlinks=opts.has_symlinks)
File "/home/nyue/projects/ParaView/superbuild/paraview-superbuild_git/superbuild/cmake/scripts/fixup_bundle.unix.py", line 637, in _install_binary
shutil.copy(binary.path, app_dest)
File "/home/nyue/projects/ParaView/superbuild/qt-build/install/lib/python3.9/shutil.py", line 418, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
File "/home/nyue/projects/ParaView/superbuild/qt-build/install/lib/python3.9/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory:
'/home/nyue/projects/ParaView/superbuild/qt-build/install/lib/catalyst/libcatalyst-paraview.so'
make: *** [Makefile:120: install] Error 1
CMake Error at superbuild/cmake_install.cmake:66 (message):
Failed to install the paraview/TGZ package.
Call Stack (most recent call first):
cmake_install.cmake:47 (include)
FAILED: CMakeFiles/install.util
cd /home/nyue/projects/ParaView/superbuild/qt-build && /home/nyue/systems/cmake/cmake-3.24.3-linux-x86_64/bin/cmake -P cmake_install.cmake
ninja: build stopped: subcommand failed.
I just so happen to name my out of source build directory to be called qt-build, I am also planning to have an osmesa-build directory so that I don’t mix them up (qt and osmesa options cannot be mixed).
Or are you saying that libcatalyst should be a totally different piece of software and not something that should be built via superbuild ?
I am not familiar with catalyst, I don’t use with Paraview and hence have no experience with it.
It’s an HPC thing normally, but it should be fine (it just runs the packaging script with the install destination as the place to put things instead of where CPack expects them.
Ah, ok, I see now. It just happened to look like qt/build.
If you don’t need catalyst, you can either disable it in the superbuild (ENABLE_catalyst=OFF) and possibly see where in projects/unix/paraview.bundle.unix.cmake it comes from (near line 260 or so).
