[Haskell-cafe] Cabal Testing Pain

[Carter Schonwald]

You always have to list the other modules AFAIK, otherwise cabal sdist
won't copy them! (Or at least I can't imagine why that wouldn't be the case
when writing an application. )
On Sep 27, 2014 5:54 PM, "Mike Craig" <mkscrg at gmail.com> wrote:

> Hey all, I'm trying to setup an executable cabal project, the options for
> cabal-based testing seem poor. I poked around for discussions of this but
> didn't find much. My apologies if I'm beating a dead horse.
>
> The current options, as I understand them, are
>
> 1. Split code into library, executable, and test-suite. This gets you
> single compilation but you have to list every source file in the library's
> exposed/other-modules sections.
> 2. Split code into executable and test-suite. You don't have to list the
> source files, but you get double compilation and you have to declare every
> dependency (and version!) twice.
>
> Am I missing a third (better) option, or is this the state of things?
>
> --
> Mike Craig
>
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/haskell-cafe/attachments/20140927/f68788d3/attachment.html>