commit | c113a702219e8b52aa0628875a18c03aef8167e1 | [log] [tgz] |
---|---|---|
author | Cole Faust <colefaust@google.com> | Wed May 10 14:56:11 2023 -0700 |
committer | Cole Faust <colefaust@google.com> | Tue May 16 15:46:55 2023 -0700 |
tree | e306f9646ddf0937d4c2ec0be555e518c5420aad | |
parent | 7f1171e493dbc7a5f1d6271419d8f7346e1397d0 [diff] |
Define release flags in starlark instead of make So that we have a more restricted enviornment for this new configuration axis that can also be imported into other tools more easily. Test: Manually Change-Id: Iabce1919f6d6f57a256ae144784af7c47622b54d
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.