... | ... | @@ -33,7 +33,7 @@ You can see exactly which versions of what packages GHC depends on by looking in |
|
|
# Building packages that GHC doesn't depend on
|
|
|
|
|
|
|
|
|
You can make the build system build extra packages, on which GHC doesn't strictly depend, by extending the `EXTRA_PACKAGES` variable. It's not very tidy; see tickets [\#3896](https://gitlab.haskell.org//ghc/ghc/issues/3896) and [\#3882](https://gitlab.haskell.org//ghc/ghc/issues/3882) for more information.
|
|
|
You can make the build system build extra packages, on which GHC doesn't strictly depend, by adding them to the `$(TOP)/packages` file, with an `extra` tag.
|
|
|
|
|
|
|
|
|
It should be exceptional, but you can make the build system provide per-package compiler flags, by adding some definitions in `$(TOP)/ghc.mk`, just below the comment
|
... | ... | @@ -80,8 +80,7 @@ An important classification of the boot packages is as follows: |
|
|
- **INDEPENDENT**: Independently maintained. There are quite a few of these, such as `containers`, `binary`, `haskeline` and so on. Indeed most boot libraries are INDEPENDENT.
|
|
|
|
|
|
|
|
|
INDEPENDENT libraries have a
|
|
|
master repository somewhere separate from the GHC repositories. Whenever we release GHC, we ensure that the INDEPENDENT boot libraries that come with GHC are precisely sync'd with a particular released version of that library.
|
|
|
INDEPENDENT libraries have a master repository somewhere separate from the GHC repositories. Whenever we release GHC, we ensure that the INDEPENDENT boot libraries that come with GHC are precisely sync'd with a particular released version of that library.
|
|
|
|
|
|
## Zero-boot packages
|
|
|
|
... | ... | |