| commit | 1c8080098a5b5198a2cf48367df1548085666efb | [log] [tgz] |
|---|---|---|
| author | Tianjie Xu <xunchang@google.com> | Wed Sep 11 00:29:26 2019 -0700 |
| committer | Tianjie Xu <xunchang@google.com> | Wed Sep 11 15:23:41 2019 -0700 |
| tree | a51499c9a0b52b05f5fc012fd6be1379e7f67780 | |
| parent | d30a949547c2554421e862e9204c8da84f72dc30 [diff] |
Remove vendor & product in secondary payload We used to carry the full OTA for vendor and product partitions when generating the secondary payload. Since they are not actually used, we can remove them to reduce the size of factory OTA packages. For example, the size for a sargo package reduces from 454M to 283M after the change. Bug: 140771390 Test: generate and apply a second payload on Pixel Change-Id: I091dc07db8c345b182d9f5dd8d48f5c209245641
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.