| commit | 2e8bb7989edbb0998cd8bc70a51c06b857d54bd4 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Mon Mar 21 16:43:49 2022 -0700 |
| committer | Cole Faust <colefaust@google.com> | Tue Apr 05 16:53:38 2022 -0700 |
| tree | 4cdc0eeb7dbcd82d672c4f4087f800573570acd6 | |
| parent | 0472730380dcbe9500ab14feab29f052baa5b386 [diff] |
Add artifact path requirement support to Starlark
Artifact path requirements requires setting some new variables,
and also dumping the state of the product config variables
after evaluating partial products that set artifact path requirements.
Bug: 188079133
Test: Removed the code that disabled artifacts path requirements from the rbc dashboard script,
and verified that it was still green for aosp_arm64
Change-Id: I228e35285d788f4c83aa695c0f28b7c7db02544c
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.