| commit | 65c1162eb5ed4b670360e3f1025fe51a43c84f9d | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Mon Oct 02 12:45:30 2023 -0700 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Mon Nov 06 12:37:49 2023 -0800 |
| tree | de48ca9b9a892730115294213e496fe54f79978c | |
| parent | 54e9262f99a64c2ff641360642504c9c9e0878c7 [diff] |
Generate incremental OTAs for 16K/4K boot option Previously, the 16K/4K boot options OTAs are full OTAs, resulting in file size of ~20MB each, and ~40M for both OTAs. To reduce the space usage, use incremental OTAs instead. Test: th Bug: 302759296 Bug: 293313353 Change-Id: I61cc84c6c13f151dd6bc5ff37dd31daa5fb31abd
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.