| commit | f51b5148d587a5d482444706112677786e0e7eda | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Sat Dec 07 00:10:39 2024 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Sat Dec 07 00:10:39 2024 +0000 |
| tree | 11b4e08913531f63e3bf55f4ac2b3d94889e27b6 | |
| parent | c1fc82ffb852b4022024af3c1be9eca3c02ae374 [diff] |
Define otacerts.recovery By removing `recovery_available` property from "otacerts" and defining a dedicated recovery-specific module for "otacerts". `recovery_available` property should be used to allow the reverse dependencies recovery modules to depend on the module, not to install the module to the recovery partition. Test: m soong_generated_recovery_filesystem_test Bug: 381888358 Change-Id: I1529f072f124663d882081c001903d0bd04ce9d3
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.