commit | 5d2cf578d6b64e03d0babac436dfbbb4f9886971 | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Wed Dec 22 12:55:55 2021 +0800 |
committer | Bowgo Tsai <bowgotsai@google.com> | Wed Dec 22 13:11:32 2021 +0800 |
tree | d3864ba686a5deaee79d6e7b1b06138aafaa7124 | |
parent | cf7300e9c2c9a524c91f2592cf1746e14ab9312e [diff] |
Removing gsi_keys.mk It's no longer required to install the compliance GSI public keys into the ramdisk. Those public keys just need to be included in the VTS test suite for GSI verification. Bug: 176869478 Test: TreeHugger Change-Id: I26c4a1c7dba28a3c8cf88af64d8539fdc23a4f28
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.