| commit | d1dfcda616aebc4e0259703d29b3f939afb75662 | [log] [tgz] |
|---|---|---|
| author | Zhenhuang Wang <zeek@google.com> | Fri Feb 17 17:48:24 2023 +0800 |
| committer | Zhenhuang Wang <zeek@google.com> | Fri Feb 17 17:48:24 2023 +0800 |
| tree | 4f563d71722caadc4adaa32207153e5a1d158fb2 | |
| parent | 4e7daf65467299e3b26631e5a71ed28434982c50 [diff] |
Enable `-sha256` feature to device-tests.zip With `-sha256` flag, file header of generated zip files contains SHA256 checksum for each file, which can then be used by downstream systems. Bug: 259513199 Test: m dist device-tests Change-Id: Id5d2cba9096983da4f4843146a5eaa84393b4880
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.