Hi Jurriaan,
not quite sure I understand what you need, but if B.cabal file does not have a
Library section, there is nothing to register. It is only executable.
If you have sources of both packages and you're using sandboxing for A, than
inside the package A directory you can do:
cabal sandbox add-source path/package_B
so cabal should use source files from B to compile A.
(Not sure if you should add the Library section in B for compilig A.)
Best regards,
vlatko
-------- Original Message --------
Subject: [Haskell-cafe] Another Cabal question
From: Jurriaan Hage
Dear all,
I have another issue: I have a Cabal package (call it A) that runtime depends on another (say B), where B provides (only) an executable that is compiled with the Make build-type.
Now, I would like to list B under the build-depends of A (since there is no way to specify having just a run-time dependency), but it seems that when I cabal install B the package is not registered (although the executable does in fact become available to use within the standard directory.) So when I then compile A with Cabal it will complain the package is not registered.
Does anyone know whether the behaviour for B is normal, or whether this is a bug of some kind? If the former, what is an easy and clean way of dealing with this situation.
best, Jur
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe