On Fri, Aug 31, 2012 at 05:58:13PM +0200, Simon Hengel wrote: > > The library component of Haddock is still not build with GHC. Would it > be sane to build/include the library component of Haddock with GHC, so > that there is only one "build flavor" of Haddock?
I suspect the current setup predates the ability for executables to depend on libraries in the same Cabal package. I'd suggest that the haddock executable should be changed to depend on the haddock library, and as far as I can see there is no reason why that should cause problems in the GHC build. The library currently only seems to expose a single module; is that right? It also includes Main as non-exposed module, which while it is fine in principle seems a little odd. Perhaps most of Main should be moved into a separate module? > If yes, I'd still > tend to add "exposed: False" to Haddock's cabal file. What's the advantage in doing that? Thanks Ian _______________________________________________ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc
