commit | 0dbd877e5fccdae097104622b39cf16a0b9c7529 | [log] [tgz] |
---|---|---|
author | Cloud You <cloud.you@realtek.com> | Wed Jan 10 15:12:39 2024 +0800 |
committer | Cloud You <cloud.you@realtek.com> | Wed Jan 10 15:12:39 2024 +0800 |
tree | f8c3348f2e27c33d7a9793e6828b5cc6edd96219 | |
parent | 3939d1ca5957571814933cc311655840a513677e [diff] |
Fixed not mapping sdk_sandbox key to vendor key Some apps are signed with default sdk_sandbox key. It results in failure of GtsPackageSignatureTest Bug: 318798881 Test: run gts -m GtsPackageSignatureTest Change-Id: I676f48eb2844866f4e61af60d78026a87303d15a
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.