| commit | cd53a895996b16fedc044e535e09f4dacd0a8271 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Fri Jan 19 10:29:52 2018 -0800 |
| committer | Tao Bao <tbao@google.com> | Fri Jan 19 11:15:42 2018 -0800 |
| tree | f54f22e2adc2fc3c0872076fd17d5b3eac7bc76a | |
| parent | 13f228ebdefeffea45221889d0288e82f9d03a35 [diff] |
releasetools: Dump mkfs/fsck/simg2img outputs on error. The output (stdout and stderr combined) would be helpful in understanding the cause of the failure. Not changing other occurrences in build_image.py yet, since it's less obvious if a failed call should be considered fatal (thus whether to dump such outputs). For example, GetVeritySize() simply returns 0 on failed calls. They deserve further clean-ups in later CLs (with unit tests). Bug: 71864688 Test: Inject errors into mke2fs/e2fsck/simg2img. `m snod` prints outputs. Test: `m snod` remains quiet on successful runs. Change-Id: I172403f6cd05bce93767265dbcb110271a68e2a8
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.