cabal

I wonder if there is a way to retrieve the module names of a cabal package from parsing the .cabal files. I have tried to use parsePackageDescription from Distribution.PackageDescription.Parse but for instance when I try parsing the .cabal of the Cabal package itself ( http://hackage.haskell.org/package/Cabal-1.18.1.2/Cabal.cabal ) the library value of PackageDescription is Nothing even though there is a library section with both exposed-modules and other.modules in the .cabal file. Is this intended or am I doing anything wrong? Also, if it is intended, does anyone know any other simple way of

I'm trying to get Cabal to install the haskell-src-meta package, and I'm having difficulty with the template-haskell dependency. The dependencies for haskell-src-meta include both template-haskell >=2.7 && <2.9, template-haskell >=2.4 && <2.7, It so happens that template-haskell versions 2.7 and later will not install on my system, but template-haskell 2.5.0.0 will install. When I'm asking Cabal to install haskell-src-meta , how do I tell it to use template-haskell == 2.5.0.0 ? Here is the full information for cabal info haskell-src-meta on my system: * haskell-src-meta (library) Synopsis:

I am having an issue with building a shared library with ghc and I think I need to rebuild my haskell packages with --enable-shared, is there an easy way to rebuild all of my packages with cabal with the flag --enable-shared? If you have a ~/.cabal/world, cabal install --reinstall --enable-shared world could work, but test with the --dry-run flag first. That will, however only take care of cabal-installed packages. If you have packages installed with your distro's package manager, the distro might also provide shared versions for those (otherwise, you'd have to do it manually). Also, it would

I'm attempting to create a test suite for my project, HaskSplit in my .cabal configuration: -- Initial HaskSplit.cabal generated by cabal init. For further -- documentation, see http://haskell.org/cabal/users-guide/ name: HaskSplit version: 0.1.0.0 synopsis: Haskell Implementation of Shamir's Secret Sharing Scheme -- description: license: MIT license-file: LICENSE author: maintainer: -- copyright: category: Security build-type: Simple -- extra-source-files: cabal-version: >=1.10 executable HaskSplit main-is: Main.hs default-language: Haskell2010 -- other-modules: other-extensions:

I'm working on a website using Yesod I have the normal build running but I can't seem to populate my database reliably. I have a second haskell program that populates the database and I've added it to my cabal file like this: executable program if flag(library-only) Buildable: False main-is: ../main.hs hs-source-dirs: dist build-depends: base , myproject , yesod-default executable init if flag(library-only) Buildable: False main-is: init.hs hs-source-dirs: Init build-depends: base , directory , persistent , persistent-sqlite , text , myproject , yesod-default The problem is that when I run

I am following the user-guide for package developing: https://www.haskell.org/cabal/users-guide/developing-packages.html#quickstart I got stuck in the Flags section. How do I pass flags to my files? Is it just at build time? I have tried to search for it, but found no useful information - just the command option --flags . cabal build -f debug doesn't work Flag Debug Description: Enable debug support Manual: True Default: False BenchMark bench-foo ghc-options: -Wall type: exitcode-stdio-1.0 default-language: Haskell2010 build-depends: base, time main-is: bench-foo.hs if flag(debug) && os

I'm writing a compiler for a class I'm taking. The class isn't specifically Haskell but I'm using Haskell to write my compiler and interpreter. I have a cabal package setup to hopefully make it easy for my prof to run/compile. I have happy and alex in the build-tools field for both executables but Cabal ignores that and then complains that it cannot find the modules that Happy and Alex should be generating. If I manually run: alex LimpScanner.x happy LimpParser.y then cabal runs perfectly. I thought I had cabal automatically running them earlier but perhaps I remember imperfectly. limp.cabal: