commit | be1029af71df8c8242580e7c7b23cf3cd68bab33 | [log] [tgz] |
---|---|---|
author | Victor Hsieh <victorhsieh@google.com> | Fri Jan 07 10:42:23 2022 -0800 |
committer | Victor Hsieh <victorhsieh@google.com> | Fri Jan 07 11:07:52 2022 -0800 |
tree | 0e1849df0f29ad8008f7cd394336990ee2fa5361 | |
parent | 097f6bc1dac659ee0a393df3d2eb532e7dd68cfe [diff] |
Add missing dependencies of fs-verity manifest APK Otheriwse, the build complains about missing files when PRODUCT_SYSTEM_FSVERITY_GENERATE_METADATA is enabled (aosp/1937717). Bug: 206326351 Test: clobber, set PRODUCT_SYSTEM_FSVERITY_GENERATE_METADATA := true, build Change-Id: I11d18914d63cab0b84ae711f2334747cb26ca234
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.