diff options
| author | Jeremy Bettis <jbettis@google.com> | 2022-03-14 17:22:37 -0600 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2022-03-16 17:25:50 +0000 |
| commit | 75ef5c31550fef031cd8153b9872d6d3fb77ac21 (patch) | |
| tree | f4c4b732f311b3fc2611cb7779ffabc1b4cf093f /builtin/inttypes.h | |
| parent | bb733b03ecda9eb4fdff4a99ee187538092aeefd (diff) | |
| download | chrome-ec-75ef5c31550fef031cd8153b9872d6d3fb77ac21.tar.gz | |
zmake: Write ninja output to a build.log file
In order to capture the memory usage report in the link stage, write all
output from ninja to a build.log file in the build dir.
For example:
`zmake build herobrine` will create files in
`build/zephyr/herobrine/build-ro/build.log` and
`build/zephyr/herobrine/build-rw/build.log`
I intend to parse this file in firmware_builder.py
BRANCH=None
BUG=b:223846977
TEST=zmake build herobrine; \
tail build/zephyr/herobrine/build-*/build.log
Change-Id: I10e1e29e945f86bbc19adf62946ea7f3aab8fc6f
Signed-off-by: Jeremy Bettis <jbettis@google.com>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3523395
Tested-by: Jeremy Bettis <jbettis@chromium.org>
Auto-Submit: Jeremy Bettis <jbettis@chromium.org>
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
Commit-Queue: Jack Rosenthal <jrosenth@chromium.org>
Diffstat (limited to 'builtin/inttypes.h')
0 files changed, 0 insertions, 0 deletions