Skip to content
/ haddock Public

Mirror of haddock repository. DO NOT SUBMIT PULL REQUESTS HERE. Use http://github.com/haskell/haddock instead!

License

Notifications You must be signed in to change notification settings

ghc/haddock

Folders and files

NameName
Last commit message
Last commit date

Latest commit

76d0f9b · Feb 6, 2018
Jan 5, 2018
Jan 2, 2016
Jan 2, 2016
Feb 6, 2018
Dec 26, 2017
Jul 3, 2017
Jul 3, 2017
Jan 5, 2018
Dec 10, 2017
Jul 3, 2017
Apr 11, 2017
Dec 12, 2014
Dec 12, 2014
Aug 23, 2014
Nov 14, 2017
Apr 25, 2017
Dec 26, 2017
Sep 3, 2014
Aug 22, 2014
Jul 5, 2009
Jul 20, 2017
Oct 17, 2010
Oct 15, 2012
Apr 11, 2017
Aug 7, 2016
Nov 20, 2017
Nov 5, 2009

Repository files navigation

Haddock, a Haskell Documentation Tool Build Status

About haddock

See Description on Hackage.

Source code documentation

Full documentation can be found in the doc/ subdirectory, in reStructedText format format.

Contributing

Please create issues when you have any problems and pull requests if you have some code.

Hacking

To get started you'll need a latest GHC release installed.

Clone the repository:

  git clone https://github.com/haskell/haddock.git
  cd haddock

and then proceed using your favourite build tool.

cabal new-build -w ghc-8.2.1
# build & run the test suite
cabal new-test -w ghc-8.2.1

Using Cabal sandboxes

cabal sandbox init
cabal sandbox add-source haddock-library
cabal sandbox add-source haddock-api
cabal sandbox add-source haddock-test
# adjust -j to the number of cores you want to use
cabal install -j4 --dependencies-only --enable-tests
cabal configure --enable-tests
cabal build -j4
# run the test suite
export HADDOCK_PATH="dist/build/haddock/haddock"
cabal test

Using Stack

stack init
stack install
# run the test suite
export HADDOCK_PATH="$HOME/.local/bin/haddock"
stack test

Git Branches

If you're a GHC developer and want to update Haddock to work with your changes, you should be working on ghc-head branch instead of master. See instructions at https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Git/Submodules for an example workflow.

The master branch usually requires a GHC from the latest GHC stable branch. The required GHC version can be inferred from the version bounds on ghc in the respective .cabal files.