This is a global flag, so it can only be specified prior to the
subcommand.  It controls the name of the cabal.project file which
new-build and related commands looks for.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Previously, these flags had no affect on new-build.
Now, they let you specify where the dist-newstyle directory
should go.

Note that if a relative path is provided, it is resolved
relative to the *project root*.  If this is undesirable,
pass an absolute path instead.

Fixes #4127.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Fixes #4133

This adds support for building foreign libraries with a given ABI version on Linux. This is enables foreign libraries to specify ABI compatibility information. This is important since ABI compatibility differs from package release versions.

Two new fields are added: lib-version-info and lib-version-linux. The former accept versions Libtool-style, the latter sets SONAME versions directly. In both cases, appropriate symlinks are installed.

Libtool accepts ABI version data via the -version-info flag, which takes current[:revision[:age]] data. This is then parsed into a major.minor.build version number. We copy this approach so that library versioning may be generalised to other operating systems than Linux.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Add sandbox lib dir to environment during cabal exec

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
Signed-off-by: Auke Booij <auke@tulcod.com>

Add test suite with two basic tests for solver space leaks.

See https://ghc.haskell.org/trac/ghc/ticket/7436#comment:6.

This is an edge case. If there is only ever one choice for the next goal, the
solver never evaluates the conflict count map. Additions to the map create a
growing thunk.

See cabal-testsuite/README.md for a detailed description
of the new architecture.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Edward Z. Yang authored 8 years ago and Edward Z. Yang committed 8 years ago

Previously, the code would unconditionally report that internal
dependencies were satisfiable, even if --exact-configuration was
provided, we're in per-component mode, and the internal lib was
NOT supplied via a --dependency parameter.  Now ./Setup configure
correctly fails at the right stage.

There is a bit of wibbling to do with compatibility package names.
I think I've gotten it right.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Edward Z. Yang authored 8 years ago and Edward Z. Yang committed 8 years ago

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Add `--index-state` support to `cabal get`

[skip ci]

Move functions for creating solver HUnit test cases into a new module.

This commit moves the utility functions from
UnitTests.Distribution.Solver.Modular.Solver to a new module,
UnitTests.Distribution.Solver.Modular.DSL.TestCaseUtils.

With this `cabal get` gains the ability to

 a) unpack and update with the .cabal revision which was
    active at the given index-state, as well as

 b) allow to unpack the most recent package version
    (while satisfying imposed version constraints) as of
    the given index-state

The `--index-state` flag can be combined with `--pristine` if only b) is
desired.

Handle undefined MIN_VERSION_base in Distribution.Utils.BinaryWithFin…

Fix copy-paste mistake in error message

Fix implementation of addBuildableCondition

Oops! Forget to delete old PkgconfigDependency during refactor

Dedicated modules for `*Dependency` types and `UnqualComponentName`

...into Distribution.Utils.Generic. Distribution.Simple.Utils moved items.

Also gets rid of `Distribution.Packages.TextClass`

Deduplicate library directory arguments when testing libraries

Edward Z. Yang authored 8 years ago and Edward Z. Yang committed 8 years ago

Now that cabal-testsuite uses a Custom setup, we can assume
that we are able to read the LBI from our build.  This is good
news, because the old algorithm didn't really work at all
(and stopped working with cabal-install-1.24.0.1)

Fixes #4108.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Since this fixes #3858

The addBuildableCondition function was added to solve the problem with
"buildable: False". The problem was that we would solve or check
dependencies on the basis of the component in question being needed, and
then at the end discover that the component is actually not buildable at
all, and if we'd known that up front we would not have solved for the
component's dependencies.

The trick that addBuildableCondition does is a syntactic transformation,
from components like:

executable blah
  buildable: False
  build-depends: foo >= 1, bar < 2
  something-else: whatever

to:

executable blah
  -- empty!

Or at least, that's the intention. In the above situation the
implementation of addBuildableCondition returns an empty CondNode:

CondNode mempty mempty []

The type at which mempty is used is important here. This transformation
is used in two places: one in the solver and the other in finalizePD.
In the solver the mempty is used at types from the PackageDescription:
Library, Executable, TestSuite etc. So in this case the transformation
works fine we end up with empty executables, test suites etc.

In finalizePD however the mempty gets used at type PDTagged (which is
sort of a union of Library, Executable etc plus none/null) and the
mempty for PDTagged is PDNull which means it does not even specify
which component we're referring to. So effectively that means instead of
ending up with an empty executable in the above example, we end up
deleting the executable entirely!

This was a change in behaviour. Prior to adding addBuildableCondition
the result of finalizePD would include non-buildable components and the
rest of the build system infrastructure was set up to skip over them
when building. The change was not noticed precisely because the rest of
the system was already set up to ignore non-buildable components.

This is not however a benign change in behaviour. In particular in
cabal-install in the install plan we end up completley forgetting about
all the non-buildable components. This means we cannot even report that
components are non-buildable when users ask to build them, because we've
completely forgotten that they exist.

So this patch keeps the original addBuildableCondition for use by the
solver since the solver uses it at sensible monoid types. The patch adds
a special version for the PDTagged type which changes the transformation
so that in the above example we end up with:

executable blah
  buildable: False
  something-else: whatever

So we've stripped out all the build-depends but we keep everything else,
including of course the "buildable: False".