| commit | d61ff0f5e2616f9e4bdd01f58cf9d712e8162f26 | [log] [tgz] |
|---|---|---|
| author | Weilun Du <wdu@google.com> | Thu May 17 15:38:59 2018 -0700 |
| committer | Weilun Du <wdu@google.com> | Tue May 29 22:24:29 2018 +0000 |
| tree | 94bab571f810b02c9c6b4ed17133ebab39998d2d | |
| parent | 591617944544fb57f0c4b418397f28491f0ffa76 [diff] |
Do not copy userdata.img into sdk_addon/system-image.zip userdata.img becomes 4GB in P and it doesn't work well with patcher in android studio. We decided to remove userdata.img in system image zip and generate userdata.img by emulator. This cl does not impact real devices. BUG: 79925096 Change-Id: I5406b28291f140e2ebdbcd7c6f684f60ac59b62b Signed-off-by: Weilun Du <wdu@google.com>
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.