| commit | fd6d294c2bcd4bba5850fda22a3fb668b453aabf | [log] [tgz] |
|---|---|---|
| author | SzuWei Lin <szuweilin@google.com> | Fri Feb 15 14:18:35 2019 +0800 |
| committer | SzuWei Lin <szuweilin@google.com> | Fri Feb 15 14:34:53 2019 +0800 |
| tree | fac419c12513b1b56b3b96120ea3d17e6653dc72 | |
| parent | 1b082c3e05dc8efe38a524a7edc0c67e836b6498 [diff] |
Fix booting problem on GSI with user build GSI doesn't include gsi_system.prop on user build, and cause some devices cannot boot GSI with user build. Some properies in gsi_system.prop do not suitable for user build, the patch create a new gsi_system_user.prop for GSI user build. Bug: 124479721 Test: boot aosp_arm64-user on a blueline device. Change-Id: Ide2bdc8e8733817afb832b50b28807768e22f011
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.