| commit | c6631fed48c49dbf1e4721986151d99b020e5d56 | [log] [tgz] |
|---|---|---|
| author | LaMont Jones <lamontjones@google.com> | Wed Oct 11 18:16:17 2023 +0000 |
| committer | LaMont Jones <lamontjones@google.com> | Mon Oct 30 23:40:04 2023 +0000 |
| tree | 73066ce37d8fa44a02a79e39043db8f158ae9f5a | |
| parent | da88660301cf8ae6412b2d58294c34a6753381c0 [diff] |
Add support for product-specific build flags 1. release config maps now specify where the flag definitions are found. 2. PRODUCT_RELEASE_CONFIG_MAPS specifies additional release config map files to use. This allows product config to specify build flags, which can then be specified by users of that product. Bug: b/302593603 Test: manual Change-Id: I660a3d88c2aaecc14d6f370bebb0d05a8cc224f2
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.