| commit | 73dd4f45f3d68e387a6a04bfb0d587707f10fb57 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Thu Oct 04 16:25:33 2018 -0700 |
| committer | Tao Bao <tbao@google.com> | Thu Oct 04 17:05:09 2018 -0700 |
| tree | a4338e1c0ef1aa8040933927cfec85f74a2225e4 | |
| parent | d1428e274881d641551dcf6968ad43078bbec7bc [diff] |
releasetools: Set default stdout and stderr in common.Run().
stdout and stderr will default to subprocess.PIPE and subprocess.STDOUT
respectively (which is the expected behavior from most of the existing
callers), unless caller specifies any of them.
Test: `m dist`
Test: python -m unittest \
test_common \
test_add_img_to_target_files \
test_ota_from_target_files \
test_validate_target_files
Change-Id: I43b3f08edfa8a9bcfe54baf9848dc705c048e327
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.