| commit | a720635be20f4fc3acd39c7b83b919140ced0f94 | [log] [tgz] |
|---|---|---|
| author | Fabien Sanglard <sanglardf@google.com> | Tue Oct 20 15:47:10 2020 -0700 |
| committer | Fabien Sanglard <sanglardf@google.com> | Wed Nov 11 17:00:22 2020 -0800 |
| tree | ffc517c792221d56f4f8fd0b6066a9fb3e4f5cb1 | |
| parent | 6f83343e7eae8fd826770009cabe1827754152f7 [diff] |
Fix zipalign alignment error Problem: Zipalign operates over several false assumptions. First it assumes that zip entries are in the same order in the body and in the Central Direcotry. Second, it assumes there are not space between entries. This makes alignment incorrect when these asserts are not true. Solution: Don't align entries by tracking bias based on input zip entry location. Calculate the expected alignment based on the out- put zip file and correct with extra padding. Fixes: 162117652 Test: Units Tests Change-Id: Ia179338f658cab18a377cba2c7c8e629089a2785
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.