One way would be to simply ask to build just what you need, e.g: $ hadrian/build.sh --flavour=devel2 --freeze1 stage2:exe:ghc-bin See https://gitlab.haskell.org/ghc/ghc/blob/master/hadrian/doc/make.md for more examples of that 'simple target' syntax. When no target is specified, hadrian will go ahead and build "everything". On 01/02/2019 11:27, Roland Senn wrote:
I switched to Hadrian. Normally I hack somewhere in the compiler. So I use "hadrian/build.sh --flavour=devel2 --freeze1" to quickly rebuild GHC after some little changes to the code.
It normally builds - library 'ghc' (Stage1, way v) - program 'ghctags' (Stage1) - program 'ghc-bin' (Stage1) - program 'haddock' (Stage1)
When hacking GHC, I never use ghctags or haddock. Building ghctags is very fast, 1-2 seconds. However building haddock takes 15 to 20 seconds.
Is there a way to teach hadrian not to build haddock and ghctags?
Many thanks! Roland _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
-- Alp Mestanogullari, Haskell Consultant Well-Typed LLP, https://www.well-typed.com/ Registered in England and Wales, OC335890 118 Wymering Mansions, Wymering Road, London, W9 2NF, England