| commit | bd2d79d3111f6c0f844780a117d719b90b8b1d2d | [log] [tgz] |
|---|---|---|
| author | Pawan Wagh <waghpawan@google.com> | Mon Apr 29 19:48:26 2024 +0000 |
| committer | Pawan Wagh <waghpawan@google.com> | Mon Apr 29 19:48:26 2024 +0000 |
| tree | 621cf115f91b20786a84764d437211fc453c2fbd | |
| parent | 8f9ca8075f90165f2a44b4d582cc85ae0be9fc72 [diff] |
Fix dependency of system img on boot_otas If BOARD_16K_OTA_MOVE_VENDOR := true is set BoardConfig, there is still dependency of system img on boot otas as it is system ota paths are being added in default installed modules. Add vendor paths whenever move vendor is set. Bug: 335022191 Test: m Change-Id: I19b41e5b9ade50f3cabf43995af36e66e09c6acf
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.