| commit | bf2d4007990e24307d1baf088e0897a22f1570f3 | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Wed Aug 30 14:40:33 2023 -0700 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Thu Aug 31 12:17:14 2023 -0700 |
| tree | c0e2c172b909a343710ad03fb06b9dc34182209d | |
| parent | ee8b6cf22dcdce344f13f1e06823a392285eb4a3 [diff] |
Resize boot_16k.img properly Bootloaders often assume boot partition to be 64MB in size. Correctly size boot_16k.img so that bootloader can verify the AVB footers. Test: th Bug: 293313353 Change-Id: I322277b10e99a41c9a262ff76e2f29c3ed16fec0
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.