a515e6e092
Since I think 2.4 h5py introduced a new way to configure mpi. Therefore, the BuildFlags are removed. I built h5py and h5py-mpi packages successfully. Not sure though whether the mpi version does actually work correctly since I don't use it.
44 lines
1.1 KiB
Nix
44 lines
1.1 KiB
Nix
{ stdenv, fetchurl, python, buildPythonPackage
|
|
, numpy, hdf5, cython, six, pkgconfig
|
|
, mpiSupport ? false, mpi4py ? null, mpi ? null }:
|
|
|
|
assert mpiSupport == hdf5.mpiSupport;
|
|
assert mpiSupport -> mpi != null
|
|
&& mpi4py != null
|
|
&& mpi == mpi4py.mpi
|
|
&& mpi == hdf5.mpi
|
|
;
|
|
|
|
with stdenv.lib;
|
|
|
|
buildPythonPackage rec {
|
|
name = "h5py-${version}";
|
|
version = "2.5.0";
|
|
|
|
src = fetchurl {
|
|
url = "https://pypi.python.org/packages/source/h/h5py/${name}.tar.gz";
|
|
sha256 = "9833df8a679e108b561670b245bcf9f3a827b10ccb3a5fa1341523852cfac2f6";
|
|
};
|
|
|
|
configure_flags = "--hdf5=${hdf5}" + optionalString mpiSupport " --mpi";
|
|
|
|
postConfigure = ''
|
|
${python.executable} setup.py configure ${configure_flags}
|
|
'';
|
|
|
|
preBuild = if mpiSupport then "export CC=${mpi}/bin/mpicc" else "";
|
|
|
|
buildInputs = [ hdf5 cython pkgconfig ]
|
|
++ optional mpiSupport mpi
|
|
;
|
|
propagatedBuildInputs = [ numpy six]
|
|
++ optional mpiSupport mpi4py
|
|
;
|
|
|
|
meta = {
|
|
description =
|
|
"Pythonic interface to the HDF5 binary data format";
|
|
homepage = "http://www.h5py.org/";
|
|
license = stdenv.lib.licenses.bsd2;
|
|
};
|
|
}
|