| commit | 518373f8af1d7a65a5ee984e66c2e78e7578d889 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Tue Jul 10 15:02:14 2018 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Wed Jul 11 12:00:56 2018 -0700 |
| tree | bb4469c7a49c173df859a597a28537c4f7fc2b5c | |
| parent | d4b9e01f3999b7a7fed24ecd2b3775d9b0d278fd [diff] |
Add more status output soong_ui now parses the output from kati into "actions" to feed into the unified status system. It also looks for errors and marks the enclosing section as failed. This adds a few more states so that error messages can be more appropriately attributed - so that all errors at the end of the buid aren't attributed to the last makefile read. Test: m Test: add some errors Change-Id: I3abdb004c82e2b99822906910cd66123c11a5099
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.