diff options
| author | SZEDER Gábor <szeder.dev@gmail.com> | 2019-06-12 16:18:28 +0200 |
|---|---|---|
| committer | SZEDER Gábor <szeder.dev@gmail.com> | 2019-06-12 17:15:27 +0200 |
| commit | dafdaafabd7929391cf5e0b21509f22bedae5ae4 (patch) | |
| tree | 53102c9be34ae88974a0ed336ec388b32f9e7fc8 /examples/BlinkOpenCR/Makefile | |
| parent | 3817dbeb2847cb33173063c6d4488bfdc18aafbb (diff) | |
Show the configuration when ARDUINO_QUIET=0
There is a bit of inconsistency between documentation and code
regarding the ARDUINO_QUIET variable: 'arduino-mk-vars.md' states
that ARDUINO_QUIET "Defaults to `0` (unset/disabled)", but the code
only checks whether it's defined or not, and doesn't check whether
it's set to '0' or something else.
Consequently, having 'ARDUINO_QUIET=0' in the Makefile or running
'make ARDUINO_QUIET=0' contadicts the documentation and doesn't print
the configuration. It also means that if someone in general prefers
not to see a screenful of configuration on each build and therefore
has 'ARDUINO_QUIET = 1' in the project's Makefile or 'config.mak',
then there is no way to override it from the command line in the odd
case when showing the configuration is desired.
Modify the corresponding condition in Arduino.mk to check whether
ARDUINO_QUIET is set to 0 and treat an undefined ARDUINO_QUIET
variable as "set to 0" as well.
Diffstat (limited to 'examples/BlinkOpenCR/Makefile')
0 files changed, 0 insertions, 0 deletions
