cabal executable using local hsc modules

Andreas Voellmy andreas.voellmy at gmail.com
Mon Mar 25 19:00:40 CET 2013


OK, I will use build-depends. It works well. Thanks!


On Mon, Mar 25, 2013 at 1:54 PM, Henning Thielemann <
lemming at henning-thielemann.de> wrote:

>
> On Mon, 25 Mar 2013, Andreas Voellmy wrote:
>
>  OK, I just realized that the correct way of handling this is to use the
>> "other-modules" field of the
>> executable section. In this instance, just adding "other-modules: A" in
>> the executable section allows the
>> .hsc file to be found and compiled properly.
>>
>
> As I said, this can be done and up to Cabal-1.14 this was the only
> possible way. Since Cabal-1.10 importing the library to the executable
> worked somehow, but Haddock failed. Today the proper way is to import the
> library by Build-Depends which saves disk space and compilation time, but
> requires the field Cabal-Version >= 1.8.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20130325/05c1743a/attachment.htm>


More information about the Libraries mailing list