edit (August 2013): The cabal repl patches have recently been merged. This functionality will be a part of the next release. As of this writing, there is no easy-to-use analogue to cabal-dev ghci. We plan to add a cabal repl command in the future – however, at the moment this functionality is not in Cabal … Read more
So you have a project where you want to use your locally patched Netwire version and in your project you have a stack.yml, as an example: flags: {} packages: – ‘.’ extra-deps: {} resolver: lts-3.7 You also have an dependency on netwire declared in your cabal file. To use you patched Netwire in this project … Read more
I’m the one who was working on this Summer of Code project. The patches have been sent to Duncan, but he hasn’t reviewed them yet. Note that my code works at the package granularity, so you won’t get any speedup when building a single package. I’m currently working on a parallel wrapper around ghc –make, … Read more
You’ll need to use extra-lib-dirs and extra-libraries in the executable section of your .cabal file like so: name: MyApp version: 0.1.0.0 synopsis: homepage: author: simon.bourne category: build-type: Simple cabal-version: >=1.10 library exposed-modules: HelloWorld build-depends: base >= 4.7 && < 5 hs-source-dirs: src default-language: Haskell2010 executable MyApp main-is: Main.hs extra-lib-dirs: lib extra-libraries: helloWorld build-depends: base >= … Read more
As Duncan mentioned in Greg’s answer, Cabal-1.10 has support for test suites out of the box. The manual seems to have the best information that’s I’ve found regarding how to make use of this. Here’s a snippet from the manual which shows how to use the exitcode-stdio test type: foo.cabal Name: foo Version: 1.0 License: … Read more
I’ve enabled library-profiling: True in my ~/.cabal/config file. From then on, any new installations will automatically enable profiling. Unfortunately that still means I had to manually reinstall for the old packages already installed. Although, after a while of doing this manually, I now have most packages reinstalled with profiling enabled…
Cabal is moving to a more NPM-like model, which will make dependency resolution much simpler. Each installed package will keep a local copy of its dependencies, trading a little disk space for the headache of installing multiple global packages with mutually exclusive package versioning demands. Under this model, the subset of packages required to install … Read more
Let’s assume you have a mylib library, and mylib-commandline and mylib-server executables. You use hs-source-dirs for the library and each executable so that each has their own project root, avoiding double compilation: mylib/ # Project root mylib.cabal src/ # Root for the library tests/ mylib-commandline/ # Root for the command line utility + helper modules … Read more
NOTE: superseded by phadej’s answer suggesting common stanzas. Is there any way I can replace the long list of build-depends packages for the test suite with “same as for the executable, plus QuickCheck”? Not that I know of. However, there is a way to only mention the list of build-depends packages once, by structuring your … Read more
Cabal doesn’t keep track of what it’s installed, it just uses ghc’s library mechanism (or that of some other compiler if you’re not using ghc), so you can use rm -r ~/.ghc to remove all locally-installed libraries. If you have multiple ghc’s installed, and you only want to remove the libs for a specific ghc, … Read more