| commit | d6be720337bce468e4a12c7730de6d9fa4f05e34 | [log] [tgz] |
|---|---|---|
| author | LaMont Jones <lamontjones@google.com> | Wed Mar 27 17:37:32 2024 -0700 |
| committer | LaMont Jones <lamontjones@google.com> | Thu Mar 28 10:08:47 2024 -0700 |
| tree | 16b2fd483dc2f25489170d1527e78285e5885421 | |
| parent | 2594275195e1ec5fa96c16a9c0d3c0398455953e [diff] |
release_config: cleanup how default values are used Set the flag value to the default value, rather than waiting until the end to check if it was set anywhere. This matters when the flag is declared `appends=True`. Bug: none Test: manual Ignore-AOSP-First: Will CP, testing on internal first. Change-Id: I8384cf8e0e0caedb5fb5a343f8be23f37bf4dc87
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.