Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Assum non-existing flags as errors
This follows the changes appeared in #617
  • Loading branch information
qrilka committed Nov 16, 2018
1 parent b18fb2f commit f30d6cc
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions doc/build-overview.md
Expand Up @@ -91,7 +91,8 @@ specific package) and _general_ (general option `*` for flags is only available
snapshot packages that have been replaced.
* Apply the `flags` and `ghc-options` by name to these packages overwriting
any previous values coming from a snapshot. If any values are specified
but no matching package is found, it's an error.
but no matching package is found, it's an error. If a flag is not defined
in the corresponding package cabal file, it's an error.
* We are now left with the following:
* A wanted compiler version
* A map from package name to immutable packages with package config (flags, GHC options, hidden)
Expand Down Expand Up @@ -157,7 +158,9 @@ is found, it's an error. Note that flag settings are added _on top of_
previous settings in this case, and does not replace them. That is, if
previously we have `singleton (FlagName "foo") True` and now add
`singleton (FlagName "bar") True`, both `foo` and `bar` will now be
true.
true. If any flags are specified but no matching package is found,
it's an error. If a flag is not defined in the corresponding package
cabal file, it's an error.

## Apply CLI GHC options

Expand Down

0 comments on commit f30d6cc

Please sign in to comment.