| commit | 09c28d1689bc138cbe8e093e3a937442b66335d2 | [log] [tgz] |
|---|---|---|
| author | Mårten Kongstad <amhk@google.com> | Thu May 04 13:29:26 2023 +0200 |
| committer | Mårten Kongstad <amhk@google.com> | Thu May 04 14:34:55 2023 +0200 |
| tree | 0e62ea84426e3027c6355b15f16a92d6a3084677 | |
| parent | 4d2b4b047b4943eba6b66c2a64d4680cecf0a7e7 [diff] |
aconfig: add support for changing flag value based on build Teach aconfig about build IDs (continuously increasing integers). Extend the aconfig file format to allow flags to say "by default, my value is X, but starting from build ID A, it's Y, and from build ID B, it's Z". Bug: 279485059 Test: atest aconfig.test Change-Id: Idde03dee06f6cb9041c0dd4ca917c8b2f2faafdd
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.