If I'm doing development between ghci and vim, all the different
dependencies I need get linked in when required without me asking.
Similarly if I call ghc --make from the command line. But I have to
write them in manually to my *.cabal file otherwise the compilation
process will fail.
Until
On 03/05/07, Thomas Schilling [EMAIL PROTECTED] wrote:
I once used this perl script to determine the files I was actually
used (to have proper LOC stats). It uses ghc -M which usually
outputs the dependencies as makefile targets, and then grep over this
to get all the .hs files. If you have
By dependencies I
meant, library packages that GHC knows about.
For example, if I load something simple like
import System.Posix.Files
main = touchFile example
into GHCi and execute :main it prints
Loading package unix-1.0 ... linking ... done.
Oh, right. Well, then please file it as
On 03/05/07, Thomas Schilling [EMAIL PROTECTED] wrote:
Oh, right. Well, then please file it as a bug report on Cabal. I'll
be working on Cabal configs as my Summer of Code project; this is
clearly related. With a bit of luck it'll be done before end of August.
Okay. It seemed like a
On Thu, 2007-05-03 at 16:49 +0200, Thomas Schilling wrote:
By dependencies I
meant, library packages that GHC knows about.
For example, if I load something simple like
import System.Posix.Files
main = touchFile example
into GHCi and execute :main it prints
Loading package
On 3 maj 2007, at 17.53, Duncan Coutts wrote:
This is not a Cabal bug. By design, Cabal does not just pick up any
packages from the environment like --make does. One of the main points
of Cabal is to be able to explicitly track dependencies of a
package, so
we do require that they all be
If I'm doing development between ghci and vim, all the different
dependencies I need get linked in when required without me asking.
Similarly if I call ghc --make from the command line. But I have to
write them in manually to my *.cabal file otherwise the compilation
process will fail.
Until now
