Package Details: paraview-git v5.8.0.r235.g8ee4b222a2-1

Git Clone URL: (read-only, click to copy)
Package Base: paraview-git
Description: Open-source, multi-platform data analysis and visualization application
Upstream URL:
Licenses: custom, BSD
Conflicts: paraview
Provides: paraview
Submitter: GloW
Maintainer: GloW
Last Packager: GloW
Votes: 2
Popularity: 0.000000
First Submitted: 2017-09-25 09:46
Last Updated: 2020-02-20 10:26

Dependencies (39)

Required by (9)

Sources (1)

Latest Comments

1 2 Next › Last »

hacksd commented on 2020-06-01 22:24

I am getting this error when trying to build this package:

CMake Error at CMakeLists.txt:330 (message): The following modules were requested or required, but not found: ParaView::IOVisItBridge;ParaView::VisItLib.

These are not in gitmodules.

InspiringSand commented on 2020-05-26 11:54

I ran into some issues:

  • pegtl is not listed as a makedependency and this throws an error if the package is not installed. After installing pegtl explicitly, this wasn't an issue anymore.
  • Then two subsequent builds (8 cores, 16 threads, 16 GB RAM) a failure would occure.
    ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build(). Aborting...
    Rebooting and running with no RAM in use by other programs fixed this. I kept an eye on memory usage during this build. It stayed within 4-6GB for the first 30-40%, but spiked to 15GB around the point where it aborted the first two times (9000-10000/20000). Consider pinning a comment like the one in paraview-opt here as well:
  • So the third build seemed to finish, but I got vtk conflicts at the very end, so it didn't complete after all. Example:
    paraview-git: /usr/lib/python3.8/site-packages/ already exists in filesystem (owned by vtk)
    I have vtk installed as a dependency of gmsh.
    The community package paraview lists vtk as a conflict. Could you add that as well?
    Additional links:
  • @hottea: paraview-opt uses that directory intentionally as a workaround for the vtk conflict. I'm trying to figure out what the easiest way is for me to solve this if I wanna build the latest version. Would changing -DCMAKE_INSTALL_PREFIX=/usr \ to -DCMAKE_INSTALL_PREFIX=/opt/paraview \ work? Also if I do this I think I'll need to add paraview to PATH as is done at the end of the PKGBUILD file for paraview-opt. Thoughts?
  • Furthermore I noticed paraview-opt uses -DVTK_MODULE_ENABLE_VTK_IOGDAL=YES \ and -DVTK_MODULE_ENABLE_VTK_IOPDAL=YES \ which is discussed here if you want to look into it:, but I'm not sure it's relevant. Just comparing both build files.

GloW commented on 2020-02-20 10:27

@Archange : Thanks, I've updated the package.

Archange commented on 2020-02-18 18:35

@gpettinello: You’re issue has been fixed upstream.

@GloW: There has been some changes, qt5-svg is a new dependency, DPARAVIEW_USE_PYTHON=ON replaced DPARAVIEW_ENABLE_PYTHON=ON, system pugixml can now be used and there has been a nice simplification in using system dependencies in general:

hottea commented on 2019-12-20 02:04

@GloW I'm so sorry. I mean the paraview-opt pkg, not paraview-git.

GloW commented on 2019-12-19 14:26

$ pacman -Ql paraview-git | grep desktop
paraview-git /usr/share/applications/org.paraview.ParaView.desktop

Nothing is installed in /opt/

hottea commented on 2019-12-19 14:18

The desktop file is installed to /opt/paraview/share/applications/org.paraview.ParaView.desktop. This is not a proper place. GNOME could not find paraview. We should install it to /usr/share/applications. And the icon image should be installed to proper location too. We cannot simply install everything to /opt.

GloW commented on 2019-11-25 16:17

Do you have a specific version of MPI installed on your system ?

gpettinello commented on 2019-11-17 12:15

Error in compilation which is the same as paraview official package: conflicting symbol MPI_Comm

GloW commented on 2019-11-11 17:17

@xantares @Kunda Package have been updated.