commit | a0e177edba257d1da5fbe287c78d768ff363f844 | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Thu Mar 28 23:02:02 2019 +0800 |
committer | Bowgo Tsai <bowgotsai@google.com> | Mon Apr 01 18:24:35 2019 +0800 |
tree | 6f7ea2d798e975f95f1b252a8d4fed1ad1cbd2a0 | |
parent | 482e67f4eec3fb73c52453184d1aadef64e3917b [diff] |
Adding gsk_keys.mk Adds the following line into a device.mk in order to include GSI keys into the first-stage ramdisk. $(call inherit-product, $(SRC_TARGET_DIR)/product/gsi_keys.mk) Bug: 112293933 Test: make checks $OUT/ramdisk/avb/. Change-Id: I8e4a9a8dd607916a3f45a07e0ba14c58def5d8d3
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.