| commit | e8652d4cd1b38b91dd8bdf5bf55468cd4d829d89 | [log] [tgz] |
|---|---|---|
| author | Sasha Smundak <asmundak@google.com> | Fri Sep 24 08:25:17 2021 -0700 |
| committer | Sasha Smundak <asmundak@google.com> | Fri Sep 24 08:54:29 2021 -0700 |
| tree | 77bec29282a29ae1f7934ea227904aac3c062a99 | |
| parent | ad48e9cb875fcb59d9b3675938d2bc7e7033498f [diff] |
Separate output from diagnostics in Starlark product configuration. Some of the product configuration makefiles use `info` and `warning` Make's builtins for diagnostics. As running Starlark configuration generates the makefile as its output, this diagnostics has to go elsewhere. Implement `rblf_log` as the functional equivalent of `print` that writes to stderr instead of stdout and use it to implement `info` and `warning` counterparts. Fixes: 201073196 Test: manual Change-Id: Ib4d9c10566f9b20310fbee41eda67f0a621b0a84
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.