cabal executable using local hsc modules

[Andreas Voellmy]

Yes, If I rename A.hsc to A.hs, it works fine (without the "build-depends:
foo" in the cabal file).


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

>
> On Mon, 25 Mar 2013, Andreas Voellmy wrote:
>
>  Sure, I can do that, but then I get:
>> $ cabal install --disable-library-profiling
>> Resolving dependencies...
>> Configuring foo-1.0...
>> cabal: The field 'build-depends: foo' refers to a library which is defined
>> within the same package. To use this feature the package must specify at
>> least
>> 'cabal-version: >= 1.8'.
>> Failed to install foo-1.0
>> cabal: Error: some packages failed to install:
>> foo-1.0 failed during the configure step. The exception was:
>> ExitFailure 1
>>
>> Maybe I could try with cabal-version >= 1.8, but this doesn't seem like
>> it should be necessary. I wouldn't
>> need this build-depends: foo if A were just A.hs, right? So it seems odd
>> (from a user's standpoint) that I
>> need it when it is A.hsc.
>>
>
>
> I don't think that this depends on the HSC preprocessing. With A.hs it
> would be the same problem. Have you tried it?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20130325/0f33b712/attachment.htm>