| commit | dd3598da56fdc9326667b021269d7a7da9af88e5 | [log] [tgz] |
|---|---|---|
| author | Sasha Smundak <asmundak@google.com> | Tue Jan 18 15:36:22 2022 -0800 |
| committer | Sasha Smundak <asmundak@google.com> | Fri Jan 28 17:44:56 2022 -0800 |
| tree | cdf20063de4c6db27ddf8786e4620a5213f3a80e | |
| parent | e4442b7df67ffb2e879e96e731bb778b072df245 [diff] |
Output inherit trace as Make comments. Starlark configuration output is a makefile containing variable assignments. Inheritance trace is also written to stdout. Trace lines need to be comments, otherwise stdout cannot be digested by Make/Ckati. Test: manual Change-Id: I3c1ad6554ef4356f9ceff1ff3279b2eac962e9ac
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.