commit | e50bb51fa9dc42dea22c4bc6f54c5fe397f11c1d | [log] [tgz] |
---|---|---|
author | Kelvin Zhang <zhangkelvin@google.com> | Mon Aug 01 15:58:51 2022 -0700 |
committer | Kelvin Zhang <zhangkelvin@google.com> | Tue Aug 02 18:32:38 2022 +0000 |
tree | 23d5d8cd70ac972c3de79eba4d5657f0d2ecf9da | |
parent | 1fabb2a942060fe6b6082cb0f00e287e97172a78 [diff] |
Add flags to override all apex/apk keys Currently, if we want to override all apex/apk key, we must specify all apk/apex names exhaustively. This causes CLI arguments to be very long and sometimes exceeds OS's limit. Test: run signing test locally on build 8862875 on git_master Bug: 239991438 Change-Id: Idbd3b7eef9b2a27236f4ca7a27449fcdf0d2dd3f
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.