commit | 338856f92b1ca744214eb2ed20613edb0e6410ef | [log] [tgz] |
---|---|---|
author | Shashikant Baviskar <shashikant.baviskar@sony.com> | Thu Apr 12 12:11:22 2018 +0900 |
committer | Satoshi Futenma <Satoshi.Futenma@sony.com> | Thu Aug 23 10:13:20 2018 +0900 |
tree | 84e29f6c1a7b55bfa3d8f02d7e5c34d57d9fe78b | |
parent | da9f2d8fd43b14853491b0b241a9efa3b7fb3bf9 [diff] |
A/B update: Replace the zip FileHeader mechanism for update package When the update package gets larger than 2 GiB, payload.bin offset mentioned in metadata file for ota-streaming-property-files gets shifted (CrAU of payload.bin) because ZipInfo FileHeader() returns incorrect value. To solve the issue, offset is re-calculated from fixed bytes of central directory file header, filename length and extra length. This patch is to sync with update_device.py script. Test: manually create an A/B update package and run it using update_device.py Bug: 111198589 Change-Id: I9bf5a5ca24938cad3206d04af529f70d45e992c0
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.