This allows easier diffing of different BuildFlavours, including mk/flavours/validate.mk.
I have a better plan. I want to try the following:
- Put each BuildFlavour in its own file in mk/BuildFlavours/
- Let users import them by uncommenting a line in mk/build.mk
- Extra flags can be added afterwards
The advantage is that we can then use vimdiff BuildFlavour1 BuildFlavour2 to compare BuildFlavours.
Speak up if you think this is a bad idea.
Those problem is those default values are set by configure. For example, in mk/config.mk.in:
The idea of the perf buildflavour is that it matches the default build. This is almost true, except for -H64m vs -H32m and STRIP_CMD=: vs STRIP_CMD=strip (that last one has performance effect actually). I intend to reconcile these differences later.
This is a better example. In mk/config.mk.in we have:
BUILD_DOCBOOK_HTML = @BUILD_DOCBOOK_HTML@ BUILD_DOCBOOK_PS = @BUILD_DOCBOOK_PS@ BUILD_DOCBOOK_PDF = @BUILD_DOCBOOK_PDF@
So we can only explicitly switch building the docs off for certain build flavours, not switch it on.