commit | c1bb0247fb506bce8a589a441deaa7032b7c44fc | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Wed Mar 31 11:33:40 2021 +0800 |
committer | Bowgo Tsai <bowgotsai@google.com> | Wed Apr 14 23:26:14 2021 +0800 |
tree | 7739a0f79add8598edcad16b47533528403a068f | |
parent | 71c70485933b0680b1a95cba055ebbea5c8167dc [diff] |
Enable GKI 2.0 signing This is to check the interity of a generic boot.img. Note: build/make/target/product/gsi/testkey_rsa2048.pem is generated by: `openssl genrsa -out testkey_rsa2048.pem 2048`. Bug: 177862434 Test: `make bootimage` `unpack_bootimg --boot_img $OUT/boot.img --out unpack` `avbtool info_image --image ./unpack/boot_signature` Change-Id: I12ea4c666f71ad6b6c245d629e41904eb8d90858
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.