| commit | 0a6d2e54dc38132550034d6cbe9fad9db0f3cd31 | [log] [tgz] |
|---|---|---|
| author | Andrew Scull <ascull@google.com> | Mon Jul 04 17:48:35 2022 +0000 |
| committer | Andrew Scull <ascull@google.com> | Thu Jul 07 19:56:31 2022 +0000 |
| tree | 81a9dbbd3f8050c1c9323b622f041ed92ceceb1f | |
| parent | f68794510fcbfd10a38bdfbf8d5d6c1f6d206afb [diff] |
Extract fsverity_manifest_generator logic Let the fsverity_manifest_generator logic be reused and just keep the bits to generate the BuildManifest.apk. Since this can all be acheived with a series of shell commands, remove the python script and just do it directly in the Makefile. Bug: 237384936 Test: TH Change-Id: I168dc1cea0be72b5098f99e4183e080a687fb03e
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.