commit | fa9de0aae8b585c8f2f81da2921642c32523e4a2 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Mon Mar 18 10:24:17 2019 -0700 |
committer | Tao Bao <tbao@google.com> | Mon Mar 18 10:26:09 2019 -0700 |
tree | 19534bb085fd1e56606374fc4303f72d17812061 | |
parent | 0573298a182fc673cfee1c89e183b515c5383d0d [diff] |
releasetools: Fix an issue when using APEX container key mapping. The keys_info in the touched code is a tuple, which is immutable. Bug: 123716522 Test: Run sign_target_files_apks.py with '-e foo.apex=bar' that replaces the APEX container key. Change-Id: I4e57e46c93a56b7f6646764d021ebb42c19bf7f5
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.