| commit | abb806b3f0836993946382564b03cef5a72d6486 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Aug 06 10:32:32 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Tue Aug 06 14:13:19 2019 -0700 |
| tree | 0dc6da6fd7cbb7daf9cafc0c142ad9e366b70cd9 | |
| parent | 7edc2b199406eba0a39632d1a34577f399251071 [diff] |
releasetools: merge_target_files sets verbose in main. The flag would otherwise be turned on unconditionally even when importing merge_target_files as a module. As a result, `atest releasetools_test` was broken / flaky prior to this change, as PythonUnitTestResultParser doesn't like unexpected outputs in stderr. Test: `atest releasetools_test releasetools_py3_test` Change-Id: Ifd614c797d2cee3b33e4c2a7ad8e598850e9d60c
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.