| commit | 45b44d96e61921b356c4e1a0fb096e8b33b72d3e | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Mon Aug 02 19:58:14 2021 -0400 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Fri Aug 06 19:38:14 2021 -0400 |
| tree | 004bc4bf3dd941551b573a940fd20497d346e09f | |
| parent | bff4b52ce1ae95b263aa44abdd0c1bcfec6e7264 [diff] |
Make apex util detect if hashtree is present Test: sign_target_fiels_apks oriole_target_files.zip Bug: 195194430 Change-Id: I919d169ce4d66e6a1cdbfd15babde25005971a30
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.