| commit | 8d97bf5327e58588dc749f21eb8584bbc977d70d | [log] [tgz] |
|---|---|---|
| author | Sasha Smundak <asmundak@google.com> | Tue May 04 09:58:38 2021 -0700 |
| committer | Sasha Smundak <asmundak@google.com> | Wed Aug 04 17:15:16 2021 -0700 |
| tree | 4893398de70fae20b51efe47228543946cfafacb | |
| parent | ec37feb5195c22e0a6eabadac265c6c104abecbc [diff] |
Integrate Starlark-based configuration runner If RBC_PRODUCT_CONFIG variable is set, obtain product configuration variables by converting product configuration makefiles to Starlark files and then executing them. Also, introduce RBC_NO_PRODUCT_GRAPH variable to suppress product graph generation. We cannot generate product graph with Starlark, so this option allows to verify that the rest of the contents of the generated Ninja files remains the same when Starlark-based converter is used. This allows to perform the regression testing, i.e. running `RBC_NO_PRODUCT_GRAPH=t DISABLE_ARTIFACT_PATH_REQUIREMENTS=t m nothing` and `RBC_PRODUCT_CONFIG=t m nothing` should generate identical *.ninja files. Bug: 181797530 Test: Manual Change-Id: Ic6173a9640f32766b71c02a2b1833ce7a278e4cc
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.