Simon Marlow:
Simon Peyton-Jones wrote:
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:
http://hackage.haskell.org/trac/ghc/wiki/Building
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?
Yes, I think it is a good idea to have such documentation (and writing
it by lazy eval is fine of course!)
I reorg'd the top-level layout a bit (some of the getting-started
info had moved away from the front), but didn't look into the
content yet, as Ian said he'd do a pass over this when things have
settled down.
Any idea when things will have settled down? Being sick of build
failures, I have actually pretty much given up on pulling from the
head and will keep my type family patches to myself until things have
settled down. (Well, I am happy to push them, but I can't validate
them against the current head making the situation only worse, so I'd
rather hold off.)
Manuel
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
