... | ... | @@ -53,10 +53,10 @@ THREADS=1 ./validate |
|
|
|
|
|
### Configuration files
|
|
|
|
|
|
`validate` usually starts by `make maintainer-clean` to make sure that everything builds from scratch. Furthermore, it ignores the build settings you have put in `mk/build.mk`, and instead uses those in `mk/validate-settings.mk`.
|
|
|
`validate` usually starts by `make maintainer-clean` to make sure that everything builds from scratch. Furthermore, it ignores the build settings you have put in `mk/build.mk`, and instead uses those in `mk/flavours/validate.mk`.
|
|
|
|
|
|
|
|
|
You may want to validate a different configuration, e.g. with `GhcLibWays = p`. To do that, create a new file `mk/validate.mk` and put those settings in there.
|
|
|
You may want to validate a different configuration, e.g. with `GhcLibWays = p`. To do that, create a new file `mk/validate.mk` and put those settings in there. Settings in `mk/validate.mk` override those from `mk/flavours/validate.mk` (which in turn override those from `mk/config.mk`).
|
|
|
|
|
|
|
|
|
After you run `validate` your tree will continue to use the same settings. The way to get back to using your own `build.mk` is to run `make distclean`. Less brutally, simply remove the file `mk/are-validating.mk`.
|
... | ... | |