Using Haddock 2.0 to build GHC libraries

[Duncan Coutts]

On Fri, 2007-10-26 at 13:31 +0100, Simon Marlow wrote:
> This is specific to the GHC build system.  There are flags defined in 
> build.mk that are local to the build, and have to be plumbed through to 
> Cabal.  We don't want to have to reconfigure every time these flags change, 
> so they're passed to setup when we invoke it.

Just to record an earlier conversation on #ghc...

ghc does pass some options at build time but as far as we can tell these
are not critical to make things compile, they're flags like -O -fasm
etc.

$ cabal build --$PROG-option  is a nice hack for temporarily passing
extra flags to any program (it works for any program, not just ghc) but
it shouldn't be used routinely since it's specific to the build command.
We don't want to have to have that for all cabal commands. What is
specified at configure time should be enough.

So in summary, cabal haddock --$PROG-options should not be necessary, so
actually we do not know yet why the base docs are not building with
haddock-2.0.

Duncan