| commit | c7441e59071b0548ae85d4973364442e28a788a6 | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Tue Aug 22 08:56:30 2023 -0700 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Wed Aug 23 12:37:29 2023 -0700 |
| tree | 8073aa55422351802b6434716a7654bf74493c83 | |
| parent | a169e4f7f6adf948757c1865cc4fdfe669a9628b [diff] |
Add a tool to generate OTA from images During build, we will need to generate an OTA for boot partition using a 16K boot image. Typically, OTA is generated from target_files.zip . To avoid relying on target_files.zip as a dependency for 16K OTA, add a tool to generate OTA directly from a raw image. Test: th, ota_from_raw_img --partition_name boot --output ota.zip $OUT/boot_16k.img Bug: 293313353 Change-Id: I2076332faf2a8dc573450597efd481e285a49545
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.