| commit | 4bf41fda537c633b04223ddefbc490d62ede2668 | [log] [tgz] |
|---|---|---|
| author | Yeabkal Wubshit <yeabkal@google.com> | Thu Jul 11 16:24:33 2024 -0700 |
| committer | Yeabkal Wubshit <yeabkal@google.com> | Mon Jul 15 17:55:05 2024 +0000 |
| tree | 7b3b72face117695cd27803925bd821ca75bac49 | |
| parent | 32af1781752348f7fb4cb19ffe26fc8092b9c05c [diff] |
Include Wear flag values in sdk builds Wear APIs are currently not being included in sdk builds, since Wear flags are not part of the default set of flags read by the build system. To mitigate this, we are explicitly including Wear flags in the list of flags processed for sdk builds. Bug: 350775600 Test: sdk builds contain Wear flags Change-Id: I9e78a7f4282fa80a2ea30cbbc358c8e45ced0a9e
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.