| commit | 1dc07fa574abafc50d3e1767f444ea84aee1d63f | [log] [tgz] |
|---|---|---|
| author | LaMont Jones <lamontjones@google.com> | Wed Oct 11 20:12:10 2023 +0000 |
| committer | LaMont Jones <lamontjones@google.com> | Mon Oct 30 23:40:04 2023 +0000 |
| tree | bba0a3b834a668a22bf361ca218da84dd6afb33e | |
| parent | c6631fed48c49dbf1e4721986151d99b020e5d56 [diff] |
release_config: build flags can be lists Allow a build flag definition to indicate that its value should be the concatentation of assignements, rather than the final assigned value. In this case, the "default" value from the flag definition is always present as the start of the list. The initial use case for this is RELEASE_ACONFIG_VALUE_SETS, where we need apply multiple definition files that should be processed to arrive at the final value. Bug: b/302593603, b/304814040 Test: manual Change-Id: I2474cdf23341f9b1682affce6cc784281557655d
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.