commit | 36054e2daf2f57ab90c05e9a43aaa3fb428c6123 | [log] [tgz] |
---|---|---|
author | Yi-Yo Chiang <yochiang@google.com> | Sat Jan 08 22:29:30 2022 +0800 |
committer | Yi-Yo Chiang <yochiang@google.com> | Fri Jan 14 19:50:32 2022 +0800 |
tree | aa48196da1f4a802cc69178b82a959214c7b446f | |
parent | 44fb3619d1960d8ed76283a64790fc4fb853e3df [diff] |
releasetools: Android T GKI certification scheme Companion change of Iaf48a6e3d4b97fa6bfb5e1635a288b045baa248f To support new GKI certification scheme for boot.img and init_boot.img on upgrading and launching device combinations. Bug: 210367929 Bug: 211741246 Bug: 203698939 Test: atest --host releasetools_test:test_common Test: unpack_bootimg --boot_img boot.img Test: unpack_bootimg --boot_img init_boot.img Test: avbtool info_image --image out/boot_signature Change-Id: I3749297c09c3899046550e4be776acbeea37ef2e
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.