
5 Apr
2014
5 Apr
'14
4:24 p.m.
On 05/04/14 17:16, Mark Lentczner wrote:
Haddock now also relies on ghc-paths, a package that isn't in platform, nor, oddly, is in the GHC release.
So, I'm going to presume, for releases going forward, that we'll take the Haddock that comes with GHC as the Platform's haddock.
​Good?
- Mark
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
There's an if clause in the Cabal file. If we're in the GHC tree when building, we set a symbol and then Haddock knows where to look for the libs. If we aren't, *then* we require ghc-paths. AFAICT it has been this way since 2008. -- Mateusz K.