<div dir="ltr">Yes, If I rename A.hsc to A.hs, it works fine (without the "build-depends: foo" in the cabal file).</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 25, 2013 at 1:14 PM, Henning Thielemann <span dir="ltr"><<a href="mailto:lemming@henning-thielemann.de" target="_blank">lemming@henning-thielemann.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On Mon, 25 Mar 2013, Andreas Voellmy wrote:<br>
<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sure, I can do that, but then I get:<br>
$ cabal install --disable-library-profiling <br>
Resolving dependencies...<br>
Configuring foo-1.0...<br>
cabal: The field 'build-depends: foo' refers to a library which is defined<br>
within the same package. To use this feature the package must specify at least<br>
'cabal-version: >= 1.8'.<br>
Failed to install foo-1.0<br>
cabal: Error: some packages failed to install:<br>
foo-1.0 failed during the configure step. The exception was:<br>
ExitFailure 1<br>
<br>
Maybe I could try with cabal-version >= 1.8, but this doesn't seem like it should be necessary. I wouldn't<br>
need this build-depends: foo if A were just A.hs, right? So it seems odd (from a user's standpoint) that I<br>
need it when it is A.hsc.<br>
</blockquote>
<br>
<br></div>
I don't think that this depends on the HSC preprocessing. With A.hs it would be the same problem. Have you tried it?<br>
</blockquote></div><br></div>