736b295bc5
To prevent multiple Qt libraries when developing with a custom one, the Qt
support can now be activated by directly supplying the Qt libraries as an
argument (qtLib).
qtSDK and qtFull users/developers now just have to define an override such
as the following one in order to use it inside their development
environment:
vtk.override { qtLib = qt4SDK; };
The previous behavior is still the same for vtk and vtkWithQt4 end-users.
Change-Id: I517762d4ff7de46d32cc46e6e725fd62737caa52
40 lines
1.3 KiB
Nix
40 lines
1.3 KiB
Nix
{ stdenv, fetchurl, cmake, mesa, libX11, xproto, libXt
|
|
, qtLib ? null }:
|
|
|
|
with stdenv.lib;
|
|
|
|
let
|
|
os = stdenv.lib.optionalString;
|
|
majorVersion = "5.10";
|
|
minorVersion = "0";
|
|
version = "${majorVersion}.${minorVersion}";
|
|
in
|
|
|
|
stdenv.mkDerivation rec {
|
|
name = "vtk-${os (qtLib != null) "qvtk-"}${version}";
|
|
src = fetchurl {
|
|
url = "${meta.homepage}files/release/${majorVersion}/vtk-${version}.tar.gz";
|
|
md5 = "a0363f78910f466ba8f1bd5ab5437cb9";
|
|
};
|
|
|
|
buildInputs = [ cmake mesa libX11 xproto libXt ]
|
|
++ optional (qtLib != null) qtLib;
|
|
|
|
# Shared libraries don't work, because of rpath troubles with the current
|
|
# nixpkgs camke approach. It wants to call a binary at build time, just
|
|
# built and requiring one of the shared objects.
|
|
# At least, we use -fPIC for other packages to be able to use this in shared
|
|
# objects.
|
|
cmakeFlags = [ "-DCMAKE_C_FLAGS=-fPIC" "-DCMAKE_CXX_FLAGS=-fPIC" ]
|
|
++ optional (qtLib != null) [ "-DVTK_USE_QT:BOOL=ON" ];
|
|
|
|
enableParallelBuilding = true;
|
|
|
|
meta = {
|
|
description = "Open source libraries for 3D computer graphics, image processing and visualization";
|
|
homepage = http://www.vtk.org/;
|
|
license = "BSD";
|
|
maintainers = with stdenv.lib.maintainers; [ viric bbenoist ];
|
|
platforms = with stdenv.lib.platforms; linux;
|
|
};
|
|
}
|