diff options
| author | Vic Yang <victoryang@chromium.org> | 2014-05-20 12:55:09 -0700 |
|---|---|---|
| committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | 2014-05-21 04:18:23 +0000 |
| commit | 876fe28e6f48c331182441fbad50ae8868a2d1f7 (patch) | |
| tree | e8d9fd45afc487bfdb36e493441b235eedbbf66a /Makefile.rules | |
| parent | 2d4a02759dbc4119a2ecac0f7ea6189bc6165cc0 (diff) | |
| download | chrome-ec-876fe28e6f48c331182441fbad50ae8868a2d1f7.tar.gz | |
Show success message after 'make buildall'
'make buildall' spews out a long long long message, and when an error
occurs, it's sometimes hard to spot the error message. By adding a
explicit success message after a successful run, one can just look for
that success message to determine if it failed.
BUG=None
TEST=Build and see success message.
TEST=Introduce an error, build, and check there is no success message.
BRANCH=None
Change-Id: Ia5468342ad2eb5378c3e10774ed81c5c91f002a2
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/200618
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'Makefile.rules')
| -rw-r--r-- | Makefile.rules | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Makefile.rules b/Makefile.rules index 2ebff88979..a2c3cb60c4 100644 --- a/Makefile.rules +++ b/Makefile.rules @@ -68,6 +68,7 @@ all: $(out)/$(PROJECT).bin utils buildall: $(foreach b, $(boards), proj-$(b)) runtests @touch .tests-passed + @echo "$@ completed successfully!" proj-%: @echo "======= building $*"; \ |