| commit | 06dad4f3c202211bef9220697fac0594ffc67d16 | [log] [tgz] |
|---|---|---|
| author | Gurpreet Singh <gurpreetgs@google.com> | Mon Apr 29 13:20:34 2024 +0000 |
| committer | Gurpreet Singh <gurpreetgs@google.com> | Mon Apr 29 13:24:25 2024 +0000 |
| tree | 7b7824e5dffab2a95edc4034b441cbf692520ae1 | |
| parent | b5f2cdff9d8de1d73fd6c0f0ada1bccd0e08f2cc [diff] |
V is 35. It's not bromine, it's not a gauge of film: it's the next Android release. Set final state to "sdk" marking step-1 of finalization as complete. Ignore-AOSP-First: Finalization is not performed in AOSP. Bug: 335304236 Test: presubmit Change-Id: Ifebf6ce36c5aa5c987d434085ca812f18e97ad4f
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.