Changes between Version 43 and Version 44 of TestingPatches


Ignore:
Timestamp:
Jun 23, 2016 10:22:41 AM (3 years ago)
Author:
thomie
Comment:

Mention mk/flavours/validate.mk

Legend:

Unmodified
Added
Removed
Modified
  • TestingPatches

    v43 v44  
    4444
    4545=== Configuration files ===
    46 `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`.
     46`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`.
    4747
    48 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.
     48You 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`).
    4949
    5050After 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`.