Commit graph

6 commits

Author SHA1 Message Date
Vincent Laporte d8ab8ddae1 aspcud: 1.9.1 -> 1.9.4 2018-02-28 19:09:43 +01:00
Winnie Quinn abeb6af482 aspcud: add darwin platform support
This works because `gringo` now builds on Darwin.
2017-09-13 00:40:14 +02:00
Graham Christensen 073ca2b34f
aspcu: 1.9.0 -> 1.9.1 2017-02-16 07:55:25 -05:00
Jesse Haber-Kucharsky 51b04c1bf5 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 08:39:52 -05:00
Théo Zimmermann 93fbb947b3 aspcud: fix by updating the dependencies (#20086)
Depends on gringo but gringo is now maintained as part of the clingo
suite. This commit removes gringo (standalone) and replace it with
the latest version of clingo. This update follows closely the old
derivation for gringo (see 99e06fe).
2016-11-03 12:14:45 +01:00
Jesse Haber-Kucharsky 99e06fe771 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