| commit | f77e364de0cde8ca67075ec5f5a3ca8cdd5f135b | [log] [tgz] |
|---|---|---|
| author | SzuWei Lin <szuweilin@google.com> | Thu Feb 27 16:38:16 2020 +0800 |
| committer | SzuWei Lin <szuweilin@google.com> | Mon Mar 02 16:06:02 2020 +0800 |
| tree | 6f3b94ee2faa4103e741ab2e9eb8b0cbe66d675c | |
| parent | 7b285149a36f865202ba91bd52a69a744adf7a99 [diff] |
Fix signing on some GSI targets GSI targets require enabling chain partition signing, which put the GSI signing in system.ing directly instead of in vbmeta.img. Some GSI targets inherit from BoardConfigGsiCommon.mk only, ex. gsi_arm64-user, do not enable chain partition signing. The patch add these settings back. On the other hand, the emulator makefiles still requires the settings at this time. Hence, we keep these settings in BoardConfigEmuCommon.mk. Bug: 150179516 Test: make gsi_arm64-user Test: make aosp_arm64-user Change-Id: Id188e4c6a31ce0cf9b134ebae36cbd5bfae19942
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.