| commit | 01c6f6f215cc27e153744a2b69c0e90e3c338b7d | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Tue Dec 10 13:05:25 2019 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Thu Dec 12 21:32:49 2019 +0800 |
| tree | 9f0db660e5efde87d705c31f149b565399604efe | |
| parent | 3b500a7ec3c48fd226d5963a4d42f2401ae19b89 [diff] |
Adding developer_gsi_keys.mk OEMs who are willing to support booting the public Developer-GSI in locked state can add the following line into a device.mk to include the corresponding public keys into their first-stage ramdisk. $(call inherit-product, $(SRC_TARGET_DIR)/product/developer_gsi_keys.mk) Bug: 144399552 Test: make checks $OUT/ramdisk/avb/. Change-Id: I8fdefa0fb26c2d385dda1f72503d12e6fc306694
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.