| commit | 135c1f144fa8dddf58269e3c687df2271ba90a30 | [log] [tgz] |
|---|---|---|
| author | Inseob Kim <inseob@google.com> | Thu Jan 06 17:22:07 2022 +0900 |
| committer | Inseob Kim <inseob@google.com> | Fri Jan 07 09:16:42 2022 +0900 |
| tree | 6737d10e994683287fd20262258f3cb1177df41b | |
| parent | 13daf3d4a2597213ae563ec4887fe05daf4d8695 [diff] |
Move fsverity metadata generation to Makefile build_image.py has been handling fsverity metadata generation in the packing step, but it can cause issues because the metadata files are missing in the $OUT directory, and they only exist in result system.img. This change moves the generation logic into Makefile, and makes the metadata tracked by ninja graph. Bug: 206326351 Test: PRODUCT_SYSTEM_FSVERITY_GENERATE_METADATA := true and build Change-Id: I1f910d8ac6e2cc3c54f35916871733c632f18e44
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.