| commit | 341fe0290378c280cba59898aa3e129237d5a5b0 | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Wed Mar 09 15:12:58 2022 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Wed Mar 09 16:35:19 2022 +0800 |
| tree | 886d56041f39a94f49711b8a1b0022ea1e9ac0c7 | |
| parent | 842733cb6763cef7fa8d175a130501258af6ad9e [diff] |
validate_target_files: support gki_arm64 gki_arm64 is a special target to build multiple GKI boot-*.img files. It has neither system.img nor vbmeta.img. Skips checking system.img and vbmeta.img in this case. Bug: 223078405 Test: validate_target_files signed-gki_arm64-target_files-8277156.zip Change-Id: I9d3c102c11787cf70c1e1fc8e6a552f8fd19ff72
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.