ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:47:38-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/13577visit extensions were broken by modularization2024-03-07T20:47:38-05:00Kitware Robotvisit extensions were broken by modularization**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13577). Further discussion may take place here.**
---
Compile ParaView with VisItBridge.
Configure Examples/Plugins/VisItBridge ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13577). Further discussion may take place here.**
---
Compile ParaView with VisItBridge.
Configure Examples/Plugins/VisItBridge against to build against the build.
You get:
CMake Error at CMakeLists.txt:21 (ADD_VISIT_PLUGIN_READER):
Unknown CMake command "ADD_VISIT_PLUGIN_READER".
This occurred when VisItBridge was modularized.5.13 (Summer 2024)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/14017paraview does not build against external qttesting2023-06-15T09:42:45-04:00Kitware Robotparaview does not build against external qttesting**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14017). Further discussion may take place here.**
---
Paraview does not build against external QtTesting. The module name has th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14017). Further discussion may take place here.**
---
Paraview does not build against external QtTesting. The module name has the wrong case, which precludes being able to find an external QtTesting, and users do not include QtTesting_INCLUDE_DIRS or link to the library.
(Also, QtTesting itself does not export itself as a target... or even set a QtTesting_LIBRAR{Y,IES} for that matter...)https://gitlab.kitware.com/paraview/paraview/-/issues/16820convert projects to the third party update scripts2020-07-20T08:28:38-04:00Ben Boeckelconvert projects to the third party update scriptsProjects:
* [x] protobuf (submodule)
* [ ] CosmoHaloFinder
* [ ] FreezePython
* [ ] IceT
* [x] lz4
* [x] pugixml
* [x] pygments
* [x] GitSetupProjects:
* [x] protobuf (submodule)
* [ ] CosmoHaloFinder
* [ ] FreezePython
* [ ] IceT
* [x] lz4
* [x] pugixml
* [x] pygments
* [x] GitSetuphttps://gitlab.kitware.com/paraview/paraview/-/issues/19275Make the MILI reader work on Windows OS2024-03-07T20:47:09-05:00Andrew BauerMake the MILI reader work on Windows OSThe MILI reader works on Linux and Mac but now that there's more time it needs to also work for Windows. This is a follow on to
#18689.The MILI reader works on Linux and Mac but now that there's more time it needs to also work for Windows. This is a follow on to
#18689.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19515Building with external VTK and external dependencies2023-06-22T10:38:43-04:00Alexander NeumannBuilding with external VTK and external dependenciesSo I know `USE_EXTERNAL_VTK` is not supported but I got ParaView to nearly build using vcpkg (https://github.com/microsoft/vcpkg/pull/9202) using all external dependencies. The only reason this is not yet successfull is due to some files...So I know `USE_EXTERNAL_VTK` is not supported but I got ParaView to nearly build using vcpkg (https://github.com/microsoft/vcpkg/pull/9202) using all external dependencies. The only reason this is not yet successfull is due to some files not getting installed by VTK (i.e. internal VTK headers) and some setup problems using Qt5 which are solveable for me and has nothing to do with ParaView.
So I tried to force the build of ParaView fixing the above problems in the release build directory and got it to actually compile. The problem now is that ParaView crashes on startup. By debuging the problem it seems like ParaView wants to create an instance of `vtkPolyDataMapper` which it cannot find in the `NewInstanceFunctions` because it is simply missing.
So I investigated the problem a bit further and I assume it has something to do with the `vtkModuleWrapClientServer.cmake` and the `WrapClientServer.exe` which is generated and probably wraps the vtk/pv modules. So how could I achieve the correct Wrapping using an external VTK build?
So I would like to ask for some advice how I this could by solved and move on from here.https://gitlab.kitware.com/paraview/paraview/-/issues/19527PROTOBUF_USE_DLLS defined in static build due to CMake module2020-02-12T12:54:29-05:00Alexander NeumannPROTOBUF_USE_DLLS defined in static build due to CMake moduleSo after successfully integrating paraview into vcpkg using the x64-windows triplet (#19515) and external VTK I want to fix the x64-windows-static triplet where everything is build statically.
The problem I encounter is that `PROTOBUF...So after successfully integrating paraview into vcpkg using the x64-windows triplet (#19515) and external VTK I want to fix the x64-windows-static triplet where everything is build statically.
The problem I encounter is that `PROTOBUF_USE_DLLS` is defined. Since the only dependency on protobuf is ParaView itself I was wondering where this definition comes from.
After investigating I found out that CMakes FindProtobuf is doing it... so maybe protobuf should be switched over to CONFIG_MODE?https://gitlab.kitware.com/paraview/paraview/-/issues/19549update generic io library2020-05-07T15:21:34-04:00Utkarsh Ayachitupdate generic io librarythere's a new version available. need to confirm that the it still supports opening old versioned files.
cc: @berkgeveci there's a new version available. need to confirm that the it still supports opening old versioned files.
cc: @berkgeveci https://gitlab.kitware.com/paraview/paraview/-/issues/20435Update VisIt TecPlot reader2021-05-15T14:11:36-04:00Phil ChiuUpdate VisIt TecPlot readerA fix to the VisIt TecPlot binary reader was recently merged in (https://github.com/visit-dav/visit/pull/5376).
How should this be brought into ParaView? Is it preferable to update all the VisIt readers or just to cherry-pick the change ...A fix to the VisIt TecPlot binary reader was recently merged in (https://github.com/visit-dav/visit/pull/5376).
How should this be brought into ParaView? Is it preferable to update all the VisIt readers or just to cherry-pick the change I'm interested in?
Historically, it appears the latter approach was taken - https://gitlab.kitware.com/paraview/paraview/-/issues/13197https://gitlab.kitware.com/paraview/paraview/-/issues/21668building Paraview 5.11 on Fedora 372022-12-06T15:57:00-05:00Nabil G.building Paraview 5.11 on Fedora 37dear experts,
while trying to build Paraview 5.11 on Fedora 37, I hit one issue related to mpi4py.
Before trying to patch what needs to be patched, do you know whether there is already some branch which supports Python 3.11 ?
```
Singul...dear experts,
while trying to build Paraview 5.11 on Fedora 37, I hit one issue related to mpi4py.
Before trying to patch what needs to be patched, do you know whether there is already some branch which supports Python 3.11 ?
```
Singularity> lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: Fedora
Description: Fedora release 37 (Thirty Seven)
Release: 37
Codename: ThirtySeven
Singularity> python --version
Python 3.11.0
```
Regardshttps://gitlab.kitware.com/paraview/paraview/-/issues/21700Compilation errors with VisRTX2022-12-19T11:45:39-05:00LucasGasparinoBSClucas.gasparino@bsc.esCompilation errors with VisRTX# VisRTX build fail
- branch: master;
## Description
Tried to build the latest master with VisRTX ray-tracing support, but got the following error:
- VisRTXBackend.cxx:6:10: fatal error: VisRTX.h: No such file or directory
Now, I do...# VisRTX build fail
- branch: master;
## Description
Tried to build the latest master with VisRTX ray-tracing support, but got the following error:
- VisRTXBackend.cxx:6:10: fatal error: VisRTX.h: No such file or directory
Now, I do have the latest VisRTX installed (using Anari and OptiX7) and properly pointed at in the environment. And it really does not contain a VisRTX.h header, only the following includes:
- anari_library_visrtx_export.h;
- visrtx.h;
The same applies to the libs: all realted to Anari. My guess is that the change to Anari is not yet reflected in what Paraview expects, or am I missing something? Could you point me to a version of VisRTX that would work in the meantime?
Thanks!https://gitlab.kitware.com/paraview/paraview/-/issues/22196System TBB not found on Centos72023-06-26T10:39:39-04:00Nathan WoodsSystem TBB not found on Centos7When installing tbb-devel on CentOS 7.9, it places the libaries in /usr/lib64, rather than /usr/lib. Find_TBB does not seem to be able to find them, and it's not obvious how to give it the appropriate hints to do so.When installing tbb-devel on CentOS 7.9, it places the libaries in /usr/lib64, rather than /usr/lib. Find_TBB does not seem to be able to find them, and it's not obvious how to give it the appropriate hints to do so.