[ANNOUNCE] Hadrian update

Andrey Mokhov andrey.mokhov at newcastle.ac.uk
Thu Nov 16 01:07:05 UTC 2017


Dear GHC developers,

As some of you might have already noticed, Hadrian has finally been merged into the GHC tree. However it's not yet time to celebrate - there are still many issues that need to be addressed before the Make-based build system may retire.

Have a look at the README if you'd like a quick try: https://github.com/ghc/ghc/tree/master/hadrian.

Here is a quick update on the on-going development:

1) Hadrian can build GHC and can already be used as part of the CI infrastructure. However, the resulting binary does not pass the validation. Zhen Zhang is looking into this, but more help is needed. See https://github.com/snowleopard/hadrian/issues/299.

2) A major refactoring by Moritz Angermann is on the way. Moritz is primarily interested in cross compilation, but to make it work he had to get rid of the ghc-cabal utility, reorganise the build tree, and make numerous other improvements to Hadrian. See https://github.com/snowleopard/hadrian/pull/445.

3) There is currently no support for binary distribution. Ben Gamari is looking into this issue: https://github.com/snowleopard/hadrian/issues/219.

4) Dynamic linking on Windows is not implemented. Tamar Christina has kindly offered help with this: https://github.com/snowleopard/hadrian/issues/343.

5) Hadrian source code is still not fully documented and tested, and generally requires some polishing. I am currently taking care of this when not distracted by urgent bug fixes and will appreciate your help in making Hadrian easier to understand and use.

I can't believe that we seem to approach the finish line! It's been a long, tedious but also interesting project. Thank you all for helping us get this far, and I hope we'll celebrate the switch from Make to Hadrian soon.

Cheers,
Andrey

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20171116/88e6db8c/attachment.html>


More information about the ghc-devs mailing list