| commit | 359862db12c6c09c003a16efd617ada26fab833b | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Wed Mar 20 12:24:58 2019 -0700 |
| committer | Tao Bao <tbao@google.com> | Wed Mar 20 12:40:34 2019 -0700 |
| tree | b6e23adb798b3bfb82618120d6d170edd24ddd90 | |
| parent | 0ff15de32a41a00c0ef1a5dbcf2826ef9c1c87db [diff] |
Revert^2 "releasetools: check_target_files_signatures.py checks APEXes."
This reverts commit 5516d37f4197f31f714d28bb307c469a15bae5da.
The previous issue in unzipping non-matching files has been addressed
with commit a49054ca2f2959f50f3188914ec0faebc90ebcbe. This CL rolls
forward to allow dumping container certifcates for APEXes.
Bug: 128848294
Test: Run check_target_files_signatures.py on target_files.zips w/ and
w/o APEX files.
Change-Id: I662aab3d96fc40ac8e5e206e32b73ac763220b70
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.