ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-04-09T16:33:23-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/18778Unable to build examples2019-04-09T16:33:23-04:00Nicolas VuailleUnable to build examplesusing arch linux up to date (cmake 3.13.4, gcc 8.2.1, ninja 1.9.0).
I just build master (09a6d398c1f16ea64c9b737b9cd5fb1a9f5f6a31) with this cmake config : [devConf.cmake](/uploads/9f976cd748b719a9c8c2b3318be7de91/devConf.cmake) (mainly ...using arch linux up to date (cmake 3.13.4, gcc 8.2.1, ninja 1.9.0).
I just build master (09a6d398c1f16ea64c9b737b9cd5fb1a9f5f6a31) with this cmake config : [devConf.cmake](/uploads/9f976cd748b719a9c8c2b3318be7de91/devConf.cmake) (mainly activating python, mpi and testing). Compilation worked fine (excepted the binaries location, as mentionned in issue #18776 )
Then, I turned PARAVIEW_BUILD_EXAMPLES to ON and rebuild.
observations
==
* 13664 targets to rebuild: is it expected ?
* 'bin' directory created, with copy of previous binaries
* 'Examples' directory created but 'empty' (see bellow)
* no examples binaries found
details
==
```bash
$ ls Examples
CMakeFiles cmake_install.cmake CTestTestfile.cmake
```
```bash
$ ninja -t targets all | grep -i examples
Examples/CMakeFiles/install/strip.util: CUSTOM_COMMAND
Examples/install/strip: phony
Examples/CMakeFiles/edit_cache.util: CUSTOM_COMMAND
Examples/edit_cache: phony
Examples/list_install_components: phony
Examples/CMakeFiles/test.util: CUSTOM_COMMAND
Examples/test: phony
Examples/CMakeFiles/install/local.util: CUSTOM_COMMAND
Examples/install/local: phony
Examples/CMakeFiles/rebuild_cache.util: CUSTOM_COMMAND
Examples/rebuild_cache: phony
Examples/CMakeFiles/install.util: CUSTOM_COMMAND
Examples/install: phony
Examples/all: phony
/home/nicolas/ParaView/ParaView/Examples/CMakeLists.txt: phony
$ ninja Examples/all
ninja: no work to do
```
```bash
$ find . -name "Example"
$
```
I expected to find the Catalyst examples (e.g. the CxxParticlePathExample binary file) but nothing is returned.
@ben.boeckelBen BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/2710Unable to build from the CVS, problem wuth configure for TCL/TK.2019-03-05T10:53:57-05:00Kitware RobotUnable to build from the CVS, problem wuth configure for TCL/TK.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2710). Further discussion may take place here.**
---
If you build from an empty build directory there is a problem with: /usr/lo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2710). Further discussion may take place here.**
---
If you build from an empty build directory there is a problem with: /usr/local/src/vtk/ParaView/Utilities/TclTk/tcl8.4.5/unix/configure.
I have also attached CMakeCache.txt
Here is the make output (edited):
-- This is a CVS repository
-- Using Buildname: Linux-c++
running /bin/sh "/usr/local/src/vtk/build/ParaView-build/Utilities/TclTk/configure_tcltk.sh" 2>&1
checking whether to use symlinks for manpages... no
...
checking if 64bit Sparc VIS support is requested... no
checking system version (for dynamic loading)... /usr/local/src/vtk/ParaView/Utilities/TclTk/tcl8.4.5/unix/configure: line 13936: syntax error near unexpected token `)'
/usr/local/src/vtk/ParaView/Utilities/TclTk/tcl8.4.5/unix/configure: line 13936: ` OSF*)'
-- This is a CVS repository
-- Finding Atomic Data Sizes
-- Finding a 64 Bit Integer
-- Configuring done
-- Generating done
-- Build files have been written to: /usr/local/src/vtk/build/ParaView-build
make: *** No targets specified and no makefile found. Stop.
make[2]: *** [maketcltk] Error 1
make[1]: *** [Utilities/TclTk/CMakeFiles/maketcltk.dir/all] Error 2
make: *** [all] Error 2https://gitlab.kitware.com/paraview/paraview/-/issues/16103Unable to build using MPI2020-05-05T09:33:35-04:00Kitware RobotUnable to build using MPI**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16103). Further discussion may take place here.**
---
Receiving the following errors when attempting to build Paraview with Open...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16103). Further discussion may take place here.**
---
Receiving the following errors when attempting to build Paraview with OpenMPI:
Linking CXX shared library ../../../lib/libvtkVPIC-pv5.0.so
CMakeFiles/VPIC.dir/GridExchange.cxx.o: In function `GridExchange::exchangeGrid(float*)':
/software/paraview/5.0/ParaView-v5.0.1-source/VTK/ThirdParty/VPIC/GridExchange.cxx:612: undefined reference to `ompi_mpi_comm_world'
/software/paraview/5.0/ParaView-v5.0.1-source/VTK/ThirdParty/VPIC/GridExchange.cxx:612: undefined reference to `MPI_Barrier'
CMakeFiles/VPIC.dir/GridExchange.cxx.o: In function `GridExchange::exchange(int, int, float*)':
/software/paraview/5.0/ParaView-v5.0.1-source/VTK/ThirdParty/VPIC/GridExchange.cxx:674: undefined reference to `ompi_mpi_comm_world'
/software/paraview/5.0/ParaView-v5.0.1-source/VTK/ThirdParty/VPIC/GridExchange.cxx:674: undefined reference to `ompi_mpi_float'
OpenMPI version 1.10.2
GCC version 4.7.3
OS RHEL 6.5
CMAKE build file:
#!/bin/bash
ccmake -G "Unix Makefiles" -DPARAVIEW_USE_MPI:BOOL=ON \
-DCMAKE_INSTALL_PREFIX=/software/paraview/5.0/rhel_mpi \
-DMPI_CXX_COMPILER=/software/openmpi/1.10.2/gcc47/bin/mpicpp \
-DMPI_C_COMPILER=/software/openmpi/1.10.2/gcc47/mpicc \
-DMPI_C_LIBRARIES=/software/openmpi/PBS/1.10.2/gcc_47/lib
-DMPI_C_INCLUDE_PATH=/software/openmpi/PBS/1.10.2/gcc_47/include
-DCMAKE_C_COMPILER=/software/gcc/4.7.3/bin/gcc \
-DCMAKE_Fortran_COMPILER=/software/gcc/4.7.3/bin/gfortran \
-DOPENGL_INCLUDE_DIR=/usr/include \
-DOPENGL_gl_LIBRARY:STRING=/usr/lib64/libGL.so \
-DOPENGL_glu_LIBRARY:STRING=/usr/lib64/libGLU.so \
-DVTK_VPIC_USE_MPI=OFF \
-DVTK_OPENGL_HAS_OSMESA=OFF \
-DPARAVIEW_BUILD_QT_GUI:BOOL=ON \
-DVTK_OPENGL_HAS_OSMESA:BOOL=OFF \
-DVTK_USE_X:BOOL=ON \
-DBUILD_TESTING=OFF \
-DPARAVIEW_USE_MPI=ON \
-DPARAVIEW_ENABLE_PYTHON=ON \
-DPYTHON_INCLUDE_DIR=/software/python/RHEL6/2.7.3/include/python2.7 \
-DPYTHON_EXECUTABLE=/software/python/RHEL6/2.7.3/bin/python \
-DOSMESA_INCLUDE_DIR= \
-DOSMESA_LIBRARY= \
../ParaView-v5.0.1-source
Disabling MPI allows the code to build to completion https://gitlab.kitware.com/paraview/paraview/-/issues/18848Unable to choose different colormaps for different view windows of the same o...2019-03-10T18:59:40-04:00Debbie-ZUnable to choose different colormaps for different view windows of the same object in ParaView 5.6.0?I have multiple render views of the same object which I want to visualize using different preset colormaps. However, once I change the color preset in one view, this seems to be automatically applied to all other views. Has anyone else c...I have multiple render views of the same object which I want to visualize using different preset colormaps. However, once I change the color preset in one view, this seems to be automatically applied to all other views. Has anyone else come across this problem or know a workaround? Many thanks!https://gitlab.kitware.com/paraview/paraview/-/issues/20157Unable to create new directory within file browser during client-server remot...2020-10-26T11:29:48-04:00Ethan StamUnable to create new directory within file browser during client-server remote connection@utkarsh.ayachit @cory.quammen
Update: this seems to happen in any file browser, not just for extracts.
I am unable to make a new directory in the file browser while in a remote client-server connection. I do have write permissions to...@utkarsh.ayachit @cory.quammen
Update: this seems to happen in any file browser, not just for extracts.
I am unable to make a new directory in the file browser while in a remote client-server connection. I do have write permissions to make the directory from the terminal.
I can make a directory with a local connection to a binary that I built. It doesn't work during remote connection to a binary that I built. I get a pop-up saying `Unable to create directory New Folder.` when trying:
![Screen_Shot_2020-08-24_at_3.10.11_PM](/uploads/fdd330d30f5dc2a6baca562a2964e0f8/Screen_Shot_2020-08-24_at_3.10.11_PM.png)5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/1935Unable to generate animations with pvbatch in PV 2.02019-03-05T10:54:17-05:00Kitware RobotUnable to generate animations with pvbatch in PV 2.0**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=1935). Further discussion may take place here.**
---
The .pvb file produced by setting up a keyframe animation and then doing 'F...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=1935). Further discussion may take place here.**
---
The .pvb file produced by setting up a keyframe animation and then doing 'File/Save batch script' produces only a single image when rendered with pvbatch. The Tcl code in the .pvb file seems to save the keyframe information but the resulting model is only executed once.https://gitlab.kitware.com/paraview/paraview/-/issues/13104Unable to glyph vectors read from an OBJ file2018-08-23T15:17:06-04:00Kitware RobotUnable to glyph vectors read from an OBJ file**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13104). Further discussion may take place here.**
---
Put the following into an OBJ file and load it into paraview:
v 0 0 0
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13104). Further discussion may take place here.**
---
Put the following into an OBJ file and load it into paraview:
v 0 0 0
vn 1 1 1
Selecting the glyph filter results in vectors that are always aligned with the x-axis.
If the loaded file is then saved as a .vtk or .vtp file, they can then be loaded in and glyphed successfully. So it appears that the vector normal data is loaded into paraview from a .obj file, because it can be saved successfully into other formats.https://gitlab.kitware.com/paraview/paraview/-/issues/3166Unable to Import VRML 2.0 Files2017-04-20T16:16:41-04:00Kitware RobotUnable to Import VRML 2.0 Files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3166). Further discussion may take place here.**
---
I tried to import VRML 2.0 files using Paraview. I reconfirmed that it was...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3166). Further discussion may take place here.**
---
I tried to import VRML 2.0 files using Paraview. I reconfirmed that it was VRML 2.0 with the provider.
My PC is a Gateway, 512 MB RAM. Same error occurs on a Gateway laptop. Both running Win XP, SP2.
Error signature contained this data:
AppName: paraview.exe AppVer: 1.0.0.0 ModName: vtkhybrid.dll
ModVer: 0.0.0.0 Offset: 00085e7ahttps://gitlab.kitware.com/paraview/paraview/-/issues/12862unable to open any file2018-08-23T15:17:15-04:00Kitware Robotunable to open any file**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12862). Further discussion may take place here.**
---
After installing version 3.12, I am unable to open even the demo files. Pa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12862). Further discussion may take place here.**
---
After installing version 3.12, I am unable to open even the demo files. Paraview crashes after selecting a file to open.https://gitlab.kitware.com/paraview/paraview/-/issues/18661Unable to open certain netCDF files on Windows, works on Linux2019-07-03T15:20:46-04:00Alex SchuethUnable to open certain netCDF files on Windows, works on LinuxI am unable to open certain gridded netCDF files on Windows Paraview but I can successfully open them on Linux. The error I get on Windows is:![paraview_2018-12-11_23-23-20](/uploads/11ab1daa2bfc93d88ac2b10775b97947/paraview_2018-12-11_2...I am unable to open certain gridded netCDF files on Windows Paraview but I can successfully open them on Linux. The error I get on Windows is:![paraview_2018-12-11_23-23-20](/uploads/11ab1daa2bfc93d88ac2b10775b97947/paraview_2018-12-11_23-23-20.png)
Here is a link to data in the same format that works for both: https://drive.google.com/open?id=1mndMHCo5tXmO6VrzH0Rg-f0jLA0G4BxA
Here is a link to data in the same format that works for Linux but breaks on Windows: https://drive.google.com/open?id=1uvxo6ry57JeIQppviKc8cehiLqwk7i6k
Thanks for your help,
Alex Schuethhttps://gitlab.kitware.com/paraview/paraview/-/issues/16951Unable to open large ( > 4 GB?) VTK XML files on Windows2017-11-21T16:31:58-05:00Steven HahnUnable to open large ( > 4 GB?) VTK XML files on WindowsI am unable to open large VTK XML files (.vti and .vts) on Windows 7 using the either ParaView 5.1.0 or the nightly build from October 3, 2016. The same files work fine on MacOS and Linux.
![LargeBox](/uploads/f8c6f4e5ac7abaf6298877445...I am unable to open large VTK XML files (.vti and .vts) on Windows 7 using the either ParaView 5.1.0 or the nightly build from October 3, 2016. The same files work fine on MacOS and Linux.
![LargeBox](/uploads/f8c6f4e5ac7abaf6298877445e02e0c6/LargeBox.png)
[StructuredGridData.cxx](/uploads/a0bb085d33f90339c6eca9a09e281563/StructuredGridData.cxx)[ImageData.cxx](/uploads/28d9656ff5f46bde645a0cfb551a2b8e/ImageData.cxx)
I also have another vtkImageData file (3.7 GB) generated with the "Resample To Image" filter that generates several errors that may be useful in debugging.
![NeutronData](/uploads/320ef9578b7175b2a8d794b587f1e29b/NeutronData.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19415Unable to perform clipping or cell selection for unstructured meshes loaded b...2019-10-27T09:23:40-04:00Tianyi LiUnable to perform clipping or cell selection for unstructured meshes loaded by a vtkPythonAlgorithm-based readerUsing the [meshio](https://github.com/nschloe/meshio) library, I recently created a vtkPythonAlgorithm-based plugin allowing reading many additional mesh formats (GMSH, Abaqus, MED, ...), see [meshioReader](https://github.com/tianyikillu...Using the [meshio](https://github.com/nschloe/meshio) library, I recently created a vtkPythonAlgorithm-based plugin allowing reading many additional mesh formats (GMSH, Abaqus, MED, ...), see [meshioReader](https://github.com/tianyikillua/paraview-meshio-reader/blob/master/meshioReader.py) but also #19411.
Following [PythonAlgorithmExamples.py](https://gitlab.kitware.com/paraview/paraview/blob/master/Examples/Plugins/PythonAlgorithm/PythonAlgorithmExamples.py), I essentially implemented a `RequestData` method that generates a `vtkUnstructuredGrid` output.
However, it seems that cell operations can not be properly performed on the mesh.
1. Clipping or plotting over line leads to ParaView crash
2. Cell selection is erroneous
What am I missing? Do I need to implement more methods for those cell operations to work. Thanks.
![](/uploads/7f77a7457791551cb708a8f76f744428/2019-10-25_17_48_26-ParaView_5.7.0.png)https://gitlab.kitware.com/paraview/paraview/-/issues/4919unable to read files with global node/element ids2019-03-05T10:49:02-05:00Kitware Robotunable to read files with global node/element ids**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4919). Further discussion may take place here.**
---
Currently the global node/element properties are commented out in Servers/S...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4919). Further discussion may take place here.**
---
Currently the global node/element properties are commented out in Servers/ServerManager/Resources/readers.xml.
We need to uncomment them, and fix vtkExodusIIReader so it can read files with those properties.
See attached patch for a possible fix.https://gitlab.kitware.com/paraview/paraview/-/issues/20264Unable to run on AWS EC2 Windows Server instance2021-03-24T08:35:16-04:00Petr MasopustUnable to run on AWS EC2 Windows Server instanceI can't get ParaView to work on any of the EC2 instances (both with GPUs or elastic GPUs) I have set up. I have installed all of the NVIDIA drivers but ParaView crashes right after it's opened. Any ideas how to make it work? Thanks!I can't get ParaView to work on any of the EC2 instances (both with GPUs or elastic GPUs) I have set up. I have installed all of the NVIDIA drivers but ParaView crashes right after it's opened. Any ideas how to make it work? Thanks!https://gitlab.kitware.com/paraview/paraview/-/issues/20987Unable to set custom timesteps with a Python source plugin2021-11-15T14:43:26-05:00Antoine SchiebUnable to set custom timesteps with a Python source pluginYou can set custom timesteps values to a source by using the Programmable Source interface, but not by using a Python plugin.
Steps to reproduce: (Paraview 5.9.1)
* Open Paraview
* Tools -> Manage Plugins
* Load New -> Select [custom_t...You can set custom timesteps values to a source by using the Programmable Source interface, but not by using a Python plugin.
Steps to reproduce: (Paraview 5.9.1)
* Open Paraview
* Tools -> Manage Plugins
* Load New -> Select [custom_timesteps_source.py](/uploads/0161111671868728d25b73f3df1a8f11/custom_timesteps_source.py) and close the Plugin manager
* Select the newly loaded _Custom Timesteps Source_ and Apply
* Notice that under the _Information_ tab of the source, the _Time_ array is empty.https://gitlab.kitware.com/paraview/paraview/-/issues/22117Unable to use multi-gpu rendering with pvbatch using EGL ParaView2023-05-02T09:21:04-04:00Gonzalo SáezUnable to use multi-gpu rendering with pvbatch using EGL ParaViewWhen using `pvbatch` with multiple GPUs, `nvidia-smi` reports that only GPU0 is being used. To ease reproducing this on Kitware's side, here are some steps and scripts that we used:
* I handcrafted a simple python script called `test.py...When using `pvbatch` with multiple GPUs, `nvidia-smi` reports that only GPU0 is being used. To ease reproducing this on Kitware's side, here are some steps and scripts that we used:
* I handcrafted a simple python script called `test.py`.
```
from paraview import simple
renderViewSettings = simple.GetSettingsProxy('RenderViewSettings')
# Properties modified on renderViewSettings
renderViewSettings.RemoteRenderThreshold = 0.0
a = simple.Cone()
simple.Show(a)
simple.Render()
simple.SaveScreenshot("/tmp/hello.png")
import time
time.sleep(20)
```
* Now, I created a headless EGL `pvserver` using
```
mpiexec \
-np 2 -x NVIDIA_VISIBLE_DEVICES=0,1,2,3 ./pvserver --mpi --force-offscreen-rendering --displays 0 : \
-np 2 -x NVIDIA_VISIBLE_DEVICES=0,1,2,3 ./pvserver --mpi --force-offscreen-rendering --displays 1 : \
-np 2 -x NVIDIA_VISIBLE_DEVICES=0,1,2,3 ./pvserver --mpi --force-offscreen-rendering --displays 2
```
* I then connected to this `pvserver` using a QT `paraview` binary, ran `test.py`, and saw 3 GPUs being used in `nvidia-smi`. Hence, `pvserver` seems to be working fine.
* I tried then with `pvbatch` using
```
mpiexec \
-np 2 -x NVIDIA_VISIBLE_DEVICES=0,1,2,3 ./pvbatch --mpi --force-offscreen-rendering --displays 0 -- ./test.py : \
-np 2 -x NVIDIA_VISIBLE_DEVICES=0,1,2,3 ./pvbatch --mpi --force-offscreen-rendering --displays 1 -- ./test.py : \
-np 2 -x NVIDIA_VISIBLE_DEVICES=0,1,2,3 ./pvbatch --mpi --force-offscreen-rendering --displays 2 -- ./test.py
```
and I only see GPU with 0 being used.
* Does Kitware know of a solution for this? Thank you.https://gitlab.kitware.com/paraview/paraview/-/issues/13523Uncertainty Rendering2018-08-23T15:16:50-04:00Kitware RobotUncertainty Rendering**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13523). Further discussion may take place here.**
---
Add Uncertainty Rendering Plugin**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13523). Further discussion may take place here.**
---
Add Uncertainty Rendering Pluginhttps://gitlab.kitware.com/paraview/paraview/-/issues/14532UncertaintyRendering plugin not working on Windows 7 64bit2020-05-22T20:48:41-04:00Kitware RobotUncertaintyRendering plugin not working on Windows 7 64bit**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14532). Further discussion may take place here.**
---
Steps to reproduce are:
1) Load the UncertaintyRendering plugin
2) Creat...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14532). Further discussion may take place here.**
---
Steps to reproduce are:
1) Load the UncertaintyRendering plugin
2) Create Wavelet source
3) Change rendering from Outline to Uncertainty Surface
This results in the following warning:
Warning: In C:\DBD\pvs-x64\paraview\src\paraview\Plugins\UncertaintyRendering\vtkUncertaintySurfacePainter.cxx, line 326
vtkUncertaintySurfacePainter (000000001367B110): GL_ARB_multitexture is not supported.
https://gitlab.kitware.com/paraview/paraview/-/issues/11983Uncheck all in Line Chart View no longer working2019-03-05T10:38:10-05:00Kitware RobotUncheck all in Line Chart View no longer working**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11983). Further discussion may take place here.**
---
The version I use is actually 3.10.0.
In 3.8.1 if you click on the [x] ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11983). Further discussion may take place here.**
---
The version I use is actually 3.10.0.
In 3.8.1 if you click on the [x] in the "Variable" header all variables would be unchecked / checked. With the current version it is necessary to uncheck each variable manually.
It's not a really severe issue but an annoyance as I usually have quite a few variables listed.https://gitlab.kitware.com/paraview/paraview/-/issues/18176Undefined reference to `png_init_filter_functions_vsx` on ppc64le system2020-05-08T06:48:32-04:00Robert Manson-SawkoUndefined reference to `png_init_filter_functions_vsx` on ppc64le systemI cannot seem to compile the latest Paraview 5.5.0 on the PPC64le machine. I am compiling with EGL (see my `cmake` invocation below) and I get a linking error. The compilation breaks at the very last step of creating `pvserver`.
```bash...I cannot seem to compile the latest Paraview 5.5.0 on the PPC64le machine. I am compiling with EGL (see my `cmake` invocation below) and I get a linking error. The compilation breaks at the very last step of creating `pvserver`.
```bash
/path/to/build/build-gcc7-smpi/lib/libvtkpng-pv5.5.so.1: undefined reference to `png_init_filter_functions_vsx'
collect2: error: ld returned 1 exit status
```
After running `make` with `VERBOSE=2` I've extracted the following line which breaks:
```bash
/path/to/bin/g++ \
-std=c++11 -g -Wl,-rpath=/path/to/spectrum_mpi/10.1.0/lib \
-rdynamic CMakeFiles/pvserver.dir/pvserver.cxx.o \
-o ../bin/pvserver \
-Wl,-rpath,/path/to/build/lib: \
../lib/libvtkPVServerManagerApplication-pv5.5.so.1 \
../lib/libvtkPVServerManagerCore-pv5.5.so.1 \
../lib/libvtkPVServerImplementationCore-pv5.5.so.1 \
../lib/libvtkPVClientServerCoreCore-pv5.5.so.1 \
../lib/libvtkFiltersParallel-pv5.5.so.1 \
../lib/libvtkFiltersExtraction-pv5.5.so.1 \
../lib/libvtkFiltersModeling-pv5.5.so.1 \
../lib/libvtkFiltersGeometry-pv5.5.so.1 \
../lib/libvtkPVVTKExtensionsCore-pv5.5.so.1 \
../lib/libvtkPVCommon-pv5.5.so.1 \
../lib/libvtkClientServer-pv5.5.so.1 \
../lib/libvtkIOXMLParser-pv5.5.so.1 \
../lib/libvtkFiltersSources-pv5.5.so.1 \
../lib/libvtkFiltersGeneral-pv5.5.so.1 \
../lib/libvtkFiltersCore-pv5.5.so.1 \
../lib/libvtkIOImage-pv5.5.so.1 \
../lib/libvtkPVVTKExtensionsSIL-pv5.5.so.1 \
../lib/libvtkParallelMPI-pv5.5.so.1 \
../lib/libvtkParallelCore-pv5.5.so.1 \
../lib/libvtkIOLegacy-pv5.5.so.1 \
../lib/libvtkIOCore-pv5.5.so.1 \
../lib/libvtkCommonExecutionModel-pv5.5.so.1 \
../lib/libvtkCommonDataModel-pv5.5.so.1 \
../lib/libvtkCommonSystem-pv5.5.so.1 \
../lib/libvtkCommonTransforms-pv5.5.so.1 \
../lib/libvtkCommonMisc-pv5.5.so.1 \
../lib/libvtkCommonMath-pv5.5.so.1 \
../lib/libvtkCommonCore-pv5.5.so.1 \
../lib/libprotobuf.so \
-lpthread \
../lib/libvtkjsoncpp-pv5.5.so.1 \
-Wl,-rpath-link,/path/to/build
```
The script used to work with the previous version of PV 5.4.1. I would apprecaite any advice on this.
Finally, I am attaching my `cmake` invocation. Thanks!
```bash
cmake \
-DBUILD_TESTING=OFF \
-DPARAVIEW_ENABLE_CATALYST=ON \
-DPARAVIEW_ENABLE_PYTHON=ON \
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON \
-DPARAVIEW_USE_MPI=ON \
-DVTK_RENDERING_BACKEND=OpenGL2 \
-DVTK_OPENGL_HAS_EGL=ON \
-DVTK_USE_X=OFF \
-DVTK_IGNORE_CMAKE_CXX11_CHECKS=ON \
-DCMAKE_CXX_FLAGS='-std=c++11' \
-DPARAVIEW_BUILD_QT_GUI=OFF \
-DEGL_gldispatch_LIBRARY:FILEPATH=/usr/lib64/nvidia/libGLdispatch.so.0 \
-DEGL_LIBRARY=/usr/lib64/nvidia/libEGL.so \
-DEGL_opengl_LIBRARY=/usr/lib64/nvidia/libOpenGL.so \
-DCMAKE_INSTALL_PREFIX=${INSTALL_DIR} \
../ParaView-v${VERSION} && make -j16 && make install
```