Package Details: vtk-git 8.2.0.3046.g5345571164-1

Git Clone URL: https://aur.archlinux.org/vtk-git.git (read-only, click to copy)
Package Base: vtk-git
Description: A software system for 3D computer graphics, image processing, and visualization
Upstream URL: http://www.vtk.org
Licenses: BSD
Conflicts: vtk
Provides: vtk
Submitter: pmattern
Maintainer: pmattern
Last Packager: xantares
Votes: 2
Popularity: 0.000000
First Submitted: 2016-05-02 16:20
Last Updated: 2020-04-23 19:44

Dependencies (17)

Required by (68)

Sources (1)

Pinned Comments

pmattern commented on 2016-05-23 23:39

The package suffers from several problems regarding its dependencies. The well-understood ones as well as some additional notes are stated in PKBUILD. The not so well-understood ones which eventually need further investigating are as follows:
→ GLEW: A CMake option VTK_USE_SYSTEM_GLEW exists but assigning ON on the command line gets reverted to OFF and the version included in the VTK code is used. This shouldn't result in problems as the latter results in shared libraries named libvtkglew-<VTK version>.so*.
→ Java: With JAVA_HOME set as described in PKGBUILD neither cmake nor make throw any error message. Yet according to ldd twenty of the binary files of VTK don't find libjawt.so (JNI) when it's installed at the usual location.
→ XDMF: A working package isn't available in Arch Linux as xdmf from the AUR fails to build. An upstream Git checkout compiles but yields shared libraries with faulty sonames and files *.cmake that aren't recognized by VTK, even if manually moved from the wrong location implemented in cmake / make to the usual one. Compiling XDMF version 2 included in VTK against system HDF5 causes FTBFS. Thus using the included XDMF version 3 only for now.

Latest Comments

Gorgor commented on 2020-05-17 11:11

I had two problems when using this package:

  1. I used JDK 13, which doesn’t support java source/target version 1.6, which was used as the default.

  2. I had a space in one directory in the path leading to the PKGBUILD file, which caused a problem in the install command in the package function.

I got it working after applying the changes in the following diff:

diff --git a/PKGBUILD b/PKGBUILD
index 9177e1c..df66e5a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -25,7 +25,7 @@ build() {
   cd "${srcdir}/vtk"
   export JAVA_HOME=/usr/lib/jvm/default
   mkdir -p build && cd build
-  cmake $srcdir/$_pkgname \
+  cmake "$srcdir/$_pkgname" \
       -DCMAKE_INSTALL_PREFIX=/usr \
       -DCMAKE_INSTALL_LIBDIR=lib \
       -DCMAKE_BUILD_TYPE=Release \
@@ -40,6 +40,8 @@ build() {
       -DVTK_WRAP_JAVA=ON \
       -DVTK_WRAP_PYTHON=ON \
       -DVTK_MODULE_ENABLE_VTK_IOADIOS2=NO \
+      -DVTK_JAVA_SOURCE_VERSION=1.8 \
+      -DVTK_JAVA_TARGET_VERSION=1.8 \
       ..
   make
 }
@@ -48,5 +50,5 @@ package() {
   cd "${srcdir}/vtk/build"
   make DESTDIR="$pkgdir" install
   # Pack license
-  install -D -m644 $srcdir/vtk/Copyright.txt $pkgdir/usr/share/licenses/$pkgname/LICENSE
+  install -D -m644 "$srcdir/vtk/Copyright.txt" "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
 }

Stevenwalton commented on 2020-03-15 03:25

Depends needs to include pugixml. I got it working after I included this.

Salamandar commented on 2018-03-10 20:27

The PKGBUILD needs some changes

# Cmake args
-      -DBUILD_DOCUMENTATION=ON \
+      -DBUILD_DOCUMENTATION=OFF \

+      -DVTK_USE_SYSTEM_LIBHARU=OFF \
+      -DVTK_USE_SYSTEM_JSONCPP=OFF \

# package()
-  # Place XdmfConfig.cmake of internal XDMF at a more reasonable location
-  mkdir -p $pkgdir/usr/lib/cmake/XDMF && mv $pkgdir/usr/XdmfConfig.cmake $pkgdir/usr/lib/cmake/XDMF/
+  rm -rf "$pkgdir/usr/lib64"

pmattern commented on 2016-05-23 23:39

The package suffers from several problems regarding its dependencies. The well-understood ones as well as some additional notes are stated in PKBUILD. The not so well-understood ones which eventually need further investigating are as follows:
→ GLEW: A CMake option VTK_USE_SYSTEM_GLEW exists but assigning ON on the command line gets reverted to OFF and the version included in the VTK code is used. This shouldn't result in problems as the latter results in shared libraries named libvtkglew-<VTK version>.so*.
→ Java: With JAVA_HOME set as described in PKGBUILD neither cmake nor make throw any error message. Yet according to ldd twenty of the binary files of VTK don't find libjawt.so (JNI) when it's installed at the usual location.
→ XDMF: A working package isn't available in Arch Linux as xdmf from the AUR fails to build. An upstream Git checkout compiles but yields shared libraries with faulty sonames and files *.cmake that aren't recognized by VTK, even if manually moved from the wrong location implemented in cmake / make to the usual one. Compiling XDMF version 2 included in VTK against system HDF5 causes FTBFS. Thus using the included XDMF version 3 only for now.

misc commented on 2016-05-23 19:29

These changes were required for me:
http://pastebin.com/raw/NkmFJFYv

gl2ps: http://www.vtk.org/Bug/view.php?id=16083
+find_package(HDF5 REQUIRED): from a patch in paraview-git, dunno if really necessary
nc_type: seems like a typo, dunno why that didn't raise errors sooner

The PKGBUILD itself should be realigned with the repo, eg. -DVTK_INSTALL_INCLUDE_DIR:PATH=include/vtk

pmattern commented on 2016-05-21 23:10

No doubt about GitHub. It had in fact already been set in the next upload's draft here.

Regarding CMAKE_BUILD_TYPE I'm not sure, though.
I thought having the debug symbols enabled which is one consequence of setting "Debug" doesn't hurt at least as long as the package is still rather new. The package size isn't too much bigger compared to the release packages in community. So do you see any particular problem that eventually doesn't exist when "Release" is set?

doug commented on 2016-05-18 15:38

thanks for this package, I have a few suggestions:
please use https://github.com/Kitware/vtk.git as source, the download speed is MUCH faster than from kitware.com
and please add -DCMAKE_BUILD_TYPE=Release to cmake flags