|Version 4 (modified by 9 years ago) (diff),|
Layout of important files and directories
Everything starts with the main GHC repository (see Building/GettingTheSources). The buld system calls that directory
$(TOP). All the paths below are relative to
- This script allows you to get or pull all the additional repositories that you need to build GHC. The command-line interface is documented in the file itself.
Lists the packages that
darcs-allshould get or pull.
packagesis looked at only by
validatebefore committing (see TestingPatches). The script is documented in the file itself.
- What is this?
libraries/ directory contains all the packages that GHC needs to build. It has one sub-directory for each package repository (e.g.
random). Usually each such repository builds just one package but sometimes more than one (e.g DPH).
libraries/cabal-bin.hsis .... (mention the executable too)
utils directory contains support utilities that GHC uses. Some of these are themselves separate repositories that
darcs-all pulls; others are part of the main GHC repository. Typically these utilities are built once and for all when your build tree is initialised.
Why isn't libffi in utils/?
These directories contain the main GHC compiler, runtime system, and documentation.
nofib/ directories contain apparatus for testing GHC. Each is a separate repository, which can be gotten with
Stuff that appears only in a build tree
This directory appears only in the build tree. It contains the
.ofiles obtained by compiling the compiler.
ghc/stage2-inplace/Code for the stage1 and stage2 compiler.