commit | 939d37b88c15ed60896e183098c3fc8a53b7933e | [log] [tgz] |
---|---|---|
author | Seungjae Yoo <seungjaeyoo@google.com> | Mon Dec 18 17:12:38 2023 +0900 |
committer | Seungjae Yoo <seungjaeyoo@google.com> | Tue Dec 26 17:21:41 2023 +0900 |
tree | 110233bdb763b19cc38e86d8662e8c3fee43e9e0 | |
parent | c77d458a7e1025cba0c0d1624871c99632973691 [diff] |
Append root digest information of microdroid vendor into vendor.img Instead appending public key information into vendor partition, append root digest of microdroid-vendor's hashtree descriptor. The root digest would be extracted in build time with avbtool. Bug: 285855436 Test: avbtool info_image --image $ANDROID_PRODUCT_OUT/vendor/etc/avf/microdroid/microdroid_vendor.img Test: avbtool info_image --image $ANDROID_PRODUCT_OUT/vendor.img Change-Id: I930b09774a1024a2e5d30f474f1589fc1b8aa25a
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.