| commit | fabf50a5773e8e65be42876b08e73a3e87fed98c | [log] [tgz] |
|---|---|---|
| author | Chris Gross <chrisgross@google.com> | Thu May 02 12:42:09 2019 -0700 |
| committer | Chris Gross <chrisgross@google.com> | Mon May 20 18:35:22 2019 +0000 |
| tree | b41fed4445e30b48d48b6c7fb06f6e8bff73b961 | |
| parent | 6ae7967309c6a89ed3d9e463b44f71f92423ad98 [diff] |
Add merging of apexkeys and apkcerts metadata Bug: 131437873 Test: Built system-only and vendor builds for merge. Compared resulting apkcertx and apexkeys text files to that of a monolithic build, Test: Created colliding entries in both apexkeys and apkcerts text files and ensure the script exited with an appropriate error message. Test: Created unit tests to cover both non-colliding and colliding entries Change-Id: I6e42ce682ffa9059344e8cd63ba3a720c1f93452
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.