commit | b707ea02069af967d62b90589d2aea68008ff839 | [log] [tgz] |
---|---|---|
author | Kelvin Zhang <zhangkelvin@google.com> | Wed Aug 21 10:33:36 2024 -0700 |
committer | Kelvin Zhang <zhangkelvin@google.com> | Wed Aug 21 10:36:57 2024 -0700 |
tree | 7418c5eadc16c85f70a946a1f4c4495705683093 | |
parent | fa47605191ef94a7ce889aa03a691a07720771d6 [diff] |
Re-generate 4K boot OTAs using signed boot.img during signing process Currently, dev option OTAs are generated using dev-key signed boot.img On release-key devices, OTA will install successfully, but user would be using dev-key signed boot image after reverting to 4K mode, and subsequent OTAs would fail. This CL re-generates 4K boot OTA using release-key signed boot.img , which allows normal OTAs after toggling dev options. Test: th Bug: 354019928 Change-Id: I40811d6ed7a37f50edea77d245bf559b66da5a71
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.