| commit | 8948d13afc3523ffb4e28909de28a0d1fd7c3821 | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Wed Aug 21 19:35:20 2024 -0700 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Thu Aug 29 13:38:45 2024 -0700 |
| tree | a74961d07795139c634de361b0a25e1be018d016 | |
| parent | 0ad443b80cda57beae30f17d77c0b7759c2e3e4a [diff] |
Add boot_16k.img and dtbo_16k.img to target_files During signing, we need to re-generate dev option OTAs, as the 4K boot images are getting signed with a different key. To allow generating incremental OTAs for boot OTAs, include 16K variant of the boot images. Test: th Bug: 339658378 Change-Id: I0aafd5f48dbefeb2b86fd8bd93f6ce4d3f28a3cd
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.