cafkafk/nixpkgs
cafkafk/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
nixpkgs/pkgs/tools/misc/aspcud/default.nix

45 lines
1 KiB
Nix
Raw Normal View History

opam, aspcud: init packages for external solver (#16938) The opam package manager relies on external solvers to determine package management decisions it makes related to upgrades, new installations, etc. While, strictly speaking, an external solver is optional, aspcud is highly recommended in documentation. Furthermore, even having a relatively small number of packages installed quickly causes the limits of the interal solver to be reached (before it times out). Aspcud itself depends on two programs from the same suite: gringo, and clasp. On Darwin, Boost 1.55 (and thus Gringo) do not build, so we only support Aspcud on non-Darwin platforms.
2016-09-12 10:44:50 +02:00
{ stdenv, fetchurl,
Revert opam solver dependency changes - Reverts the change to the monolithic `clingo` package in favor of the previous split between `clasp` and `gringo` since `opam` works with the latter but not (for some reason) with the former. - Adds explicit non-support for Python in `gringo`. This is not necessary for opam. - Forces usage of the `std::to_string` functions in the C++ standard library instead of the incomplete alternative implementations inside of the `gringo` sources.
2016-11-12 13:26:30 +01:00
boost, clasp, cmake, gringo, re2c
opam, aspcud: init packages for external solver (#16938) The opam package manager relies on external solvers to determine package management decisions it makes related to upgrades, new installations, etc. While, strictly speaking, an external solver is optional, aspcud is highly recommended in documentation. Furthermore, even having a relatively small number of packages installed quickly causes the limits of the interal solver to be reached (before it times out). Aspcud itself depends on two programs from the same suite: gringo, and clasp. On Darwin, Boost 1.55 (and thus Gringo) do not build, so we only support Aspcud on non-Darwin platforms.
2016-09-12 10:44:50 +02:00
}:
let
aspcu: 1.9.0 -> 1.9.1
2017-02-16 13:55:25 +01:00
version = "1.9.1";
opam, aspcud: init packages for external solver (#16938) The opam package manager relies on external solvers to determine package management decisions it makes related to upgrades, new installations, etc. While, strictly speaking, an external solver is optional, aspcud is highly recommended in documentation. Furthermore, even having a relatively small number of packages installed quickly causes the limits of the interal solver to be reached (before it times out). Aspcud itself depends on two programs from the same suite: gringo, and clasp. On Darwin, Boost 1.55 (and thus Gringo) do not build, so we only support Aspcud on non-Darwin platforms.
2016-09-12 10:44:50 +02:00
in
stdenv.mkDerivation rec {
name = "aspcud-${version}";
src = fetchurl {
url = "mirror://sourceforge/project/potassco/aspcud/${version}/aspcud-${version}-source.tar.gz";
aspcu: 1.9.0 -> 1.9.1
2017-02-16 13:55:25 +01:00
sha256 = "09sqbshwrqz2fvlkz73mns5i3m70fh8mvwhz8450izy5lsligsg0";
opam, aspcud: init packages for external solver (#16938) The opam package manager relies on external solvers to determine package management decisions it makes related to upgrades, new installations, etc. While, strictly speaking, an external solver is optional, aspcud is highly recommended in documentation. Furthermore, even having a relatively small number of packages installed quickly causes the limits of the interal solver to be reached (before it times out). Aspcud itself depends on two programs from the same suite: gringo, and clasp. On Darwin, Boost 1.55 (and thus Gringo) do not build, so we only support Aspcud on non-Darwin platforms.
2016-09-12 10:44:50 +02:00
};
Revert opam solver dependency changes - Reverts the change to the monolithic `clingo` package in favor of the previous split between `clasp` and `gringo` since `opam` works with the latter but not (for some reason) with the former. - Adds explicit non-support for Python in `gringo`. This is not necessary for opam. - Forces usage of the `std::to_string` functions in the C++ standard library instead of the incomplete alternative implementations inside of the `gringo` sources.
2016-11-12 13:26:30 +01:00
buildInputs = [ boost clasp cmake gringo re2c ];
opam, aspcud: init packages for external solver (#16938) The opam package manager relies on external solvers to determine package management decisions it makes related to upgrades, new installations, etc. While, strictly speaking, an external solver is optional, aspcud is highly recommended in documentation. Furthermore, even having a relatively small number of packages installed quickly causes the limits of the interal solver to be reached (before it times out). Aspcud itself depends on two programs from the same suite: gringo, and clasp. On Darwin, Boost 1.55 (and thus Gringo) do not build, so we only support Aspcud on non-Darwin platforms.
2016-09-12 10:44:50 +02:00
buildPhase = ''
cmake -DCMAKE_BUILD_TYPE=Release \
Revert opam solver dependency changes - Reverts the change to the monolithic `clingo` package in favor of the previous split between `clasp` and `gringo` since `opam` works with the latter but not (for some reason) with the former. - Adds explicit non-support for Python in `gringo`. This is not necessary for opam. - Forces usage of the `std::to_string` functions in the C++ standard library instead of the incomplete alternative implementations inside of the `gringo` sources.
2016-11-12 13:26:30 +01:00
-DGRINGO_LOC=${gringo}/bin/gringo \
opam, aspcud: init packages for external solver (#16938) The opam package manager relies on external solvers to determine package management decisions it makes related to upgrades, new installations, etc. While, strictly speaking, an external solver is optional, aspcud is highly recommended in documentation. Furthermore, even having a relatively small number of packages installed quickly causes the limits of the interal solver to be reached (before it times out). Aspcud itself depends on two programs from the same suite: gringo, and clasp. On Darwin, Boost 1.55 (and thus Gringo) do not build, so we only support Aspcud on non-Darwin platforms.
2016-09-12 10:44:50 +02:00
-DCLASP_LOC=${clasp}/bin/clasp \
-DENCODING_LOC=$out/share/aspcud/specification.lp \
.
make
'';
installPhase = ''
mkdir -p $out/bin
cp bin/{aspcud,cudf2lp,lemon} $out/bin
mkdir -p $out/share/aspcud
cp ../share/aspcud/specification.lp $out/share/aspcud
'';
meta = with stdenv.lib; {
description = "Solver for package problems in CUDF format using ASP";
homepage = http://potasssco.sourceforge.net/;
platforms = platforms.linux;
maintainers = [ maintainers.hakuch ];
license = licenses.gpl3Plus;
};
}
Reference in a new issue Copy permalink