simonpj at microsoft.com
Fri Aug 1 04:53:13 EDT 2008
Ian, and others
Following Weds IRC chat I've made a tiny start on the kind of build-system documentation that I personally would find helpful:
The two pages listed near the top with "(new)" are the ones I've added. One is supposed to document key files and directories; the other to describe key workflows.
I do not intend that these pages become comprehensive, because comprehensive documentation is expensive to write, and falls out of date. Rather, I'd like them to be a navigational aid, to help explain where to look, and the intent behind the build system.
I suggest using lazy evaluation. For example, Roman, if it's not easy to figure out what runghc.wrapper is, add a bullet to the page, and ask Ian to fill it in. That way information gets added when and only when needed.
I have tried to point to older material rather than duplicate it. It's possible that I've missed some though.
Ian: can you check what I've written for accuracy, and perhaps fill in missing info?
Roman and others: would something like this help you? What is missing?
| -----Original Message-----
| From: Ian Lynagh [mailto:igloo at earth.li]
| Sent: 31 July 2008 19:33
| To: Simon Peyton-Jones
| Subject: Re: makign
| On Thu, Jul 31, 2008 at 07:25:31PM +0100, Simon Peyton-Jones wrote:
| > what about remaking stage 1? just 'make rebuild'? in compiler/
| Yes; stage defaults to 1 in both compiler/ and ghc/.
More information about the Cvs-ghc