commit | c9c1b864ba5a34ce9f85b642503263f434542912 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Wed Jun 26 14:54:14 2019 -0700 |
committer | Tao Bao <tbao@google.com> | Wed Jun 26 17:17:09 2019 -0700 |
tree | 7865042c74030c9da290041a6719d641d4175c89 | |
parent | 90f638d8424a0c42720cbad7ce3d5bb47b387ad7 [diff] |
releasetools: Add sanity test for sign_apex. This ensures a matching interface between sign_apex and apex_utils. The test apex `testdata/foo.apex` is generated by running `system/apex/apexer/runtests.sh`. Test: python -m unittest test_sign_apex Test: atest releasetools_test Change-Id: I7c14b1df2a3038ad206aa3e5aac084c47baaa00b
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.