This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 21 Oct, 2016 1 commit
    • Duncan Coutts's avatar
      Enable assertions in Cabal and cabal-install for devs · 78f592af
      Duncan Coutts authored
      For the moment we cannot use ghc-options at the top level in the
      cabal.project since it applies to all packages not just local ones.
      Until that is fixed, use a workaround of specifying it for the two
      local packages of interest directly.
      78f592af
  2. 20 Oct, 2016 2 commits
    • Mikhail Glushenkov's avatar
      Merge pull request #3979 from christiaanb/dynlibdir · 8cac8be3
      Mikhail Glushenkov authored
      Add `--dynlibdir`
      8cac8be3
    • Christiaan Baaij's avatar
      Add `--dynlibdir` · d2da6558
      Christiaan Baaij authored
      `--dynlibdir` indicates the directory in which dynamic libraries
      are installed. By default this setting is equal to:
      
      `$libdir/$abi`
      
      The static libraries will still end up in:
      
      `$libdir/$libsubdir`
      
      With `$libsubdir/$abi` as the default directory for dynamic
      libraries, dynamic libraries will by default end up in a
      single shared directory (per package database). This has the
      potential to reduce start-up times for dynamically linked
      executable as only one RPATH per package database will be
      needed.
      
      This commit uses the functionality defined in
      
      https://phabricator.haskell.org/D2611
      
      to tell GHC's > 8.0.1 package database that dynamic libraries
      are copied to the directories mentioned in the
      
      `dynamic-library-dirs`
      
      field.
      d2da6558
  3. 19 Oct, 2016 8 commits
  4. 18 Oct, 2016 21 commits
  5. 17 Oct, 2016 6 commits
  6. 16 Oct, 2016 2 commits
    • Duncan Coutts's avatar
      The .ghc.env fix in ghc went in at the end of August · a0881199
      Duncan Coutts authored
      Change the minimum version we use to decide if ghc supports .ghc.env
      files. Previously we declared that it required 8.0.2, but 8.0.2 is not
      out yet so this makes things hard to test.
      
      It was fixed in the 8.0.x branch at the end of August, so if ghc
      declares itself to be 8.0.1.$date from September or later, then it's ok.
      a0881199
    • Duncan Coutts's avatar
      Generate .ghc.environment files for projects · efe9f19c
      Duncan Coutts authored
      This is most of the way there but needs testing in practice with
      ghc-8.0.2.
      efe9f19c