| commit | 2d0349334144e69597d63ad62e21a267bc1f31ce | [log] [tgz] |
|---|---|---|
| author | Inseob Kim <inseob@google.com> | Mon Dec 13 14:04:00 2021 +0900 |
| committer | Inseob Kim <inseob@google.com> | Wed Dec 15 09:41:29 2021 +0900 |
| tree | 3f7c5c3e4ffeb08a79ba6647a928cd6e29cd0a48 | |
| parent | 46c84edacf8b1fd0adc85a50ab59ee8f8c1e7b66 [diff] |
Add fsverity_metadata_generator helper binary Making this a host tool will help users generate their own fsverity metadata easily. Bug: 205987437 Test: m fsverity_metadata_generator and run it Change-Id: Iafd228815a74d298d87ca1466c6909c0d24c5874
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.