Hadrian update

Andrey Mokhov andrey.mokhov at newcastle.ac.uk
Mon Feb 6 03:19:28 UTC 2017

Hello everyone,

This is a quick update on the current state of Hadrian, the new build system for GHC (https://github.com/snowleopard/hadrian).

Current status

We've been slowly but steadily fixing issues, and are getting close to the stage where GHC-devs can start using Hadrian in their everyday development, perhaps at first alongside Make as a fallback option.

Here are key remaining issues and what we plan to do about them:

* Build rules for distribution and installation are not fully implemented. I don't understand very well the requirements for these build rules and plan to spend some time with Simon Marlow to complete the implementation in March. If anyone can do this earlier, feel free to volunteer, I'm happy to help.

* Ability to build stage1 GHC only. This is a quick fix on Hadrian's side but is currently blocked by Shake refactoring. Neil Mitchell is working on this.

* Hadrian can't build GHC in the dynamic way. Jose Calderon has bravely taken up the challenge to fix this oldest surviving ticket (#4).

There are a lot of other minor issues and continuous refactoring, but I think the above three are most important. If I missed anything, please let me know.

How to help

1) One of the simplest way to help the project is to try Hadrian and report any issues you encounter. To try it, clone it into your GHC tree and run it using "hadrian/build.sh" or "hadrian/build.bat", adding "-j --flavour=quickest" to speed things up. See the README for more details:


2) Whenever you are doing any changes in the GHC that affect the build system, please CC me (@snowleopard) to the corresponding Phab differential. This can save me a lot of time when Hadrian breaks because of changes in GHC.

3) Email me if you have time to write some code or docs for Hadrian - I'll find a good place to start with.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20170206/51b12cec/attachment.html>

More information about the ghc-devs mailing list