| commit | 5f1281714f1bd74f277fee482f629f929f17e22e | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Wed Jan 22 00:06:58 2025 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Wed Jan 22 01:01:51 2025 +0000 |
| tree | 7d19960a04b38ae7f6a99b3e6a70221fdf79fb64 | |
| parent | d8b5bade7de554a7d43fbc74117bc6cc5b523f5d [diff] |
Determine build_ota_package based on recovery.fstab install location recovery_fstab can be installed even if is not defined via TARGET_RECOVERY_FSTAB_GENRULE. This change modifies the conditional in determining build_ota_package to take such scenarios into account. Test: m otapackage Change-Id: Ia859b63aab902920ef7f44e4d8e09537e0e9dfad
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.