On Thu, 2009-06-04 at 12:57 +1000, John Lask wrote: > The issue you are experiencing is the result of ghci not using import > libraries to resolve external symbols. Just a bit of explanation for > reference, which will also help you understand the solution to your problem.
[..] > The long and the short of it is --- much work still needs to be > done to ensure that building and maintaining packages on windows > platforms via cabal and ghc is painless - so far every > package I have used that relied on external libraries has required > some tweaking (and not just setting library paths). Thanks for the detailed writeup. We would of course like to have better support on Windows in cabal and ghc for packages that bind C libs. Perhaps you can file some tickets with concrete suggestions? http://hackage.haskell.org/trac/hackage/ http://hackage.haskell.org/trac/ghc/ Duncan _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
