commit | 30c7aead845eebb30d1ed7ca0277450711719fe2 | [log] [tgz] |
---|---|---|
author | Treehugger Robot <treehugger-gerrit@google.com> | Fri Jul 29 23:06:22 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jul 29 23:06:22 2022 +0000 |
tree | b8d3c0ee1650c88b88acad237b10af4f468e150c | |
parent | 89c59b8fa59cb2a96044f179b5e356636b6d9ac0 [diff] | |
parent | f6f6c2f8cfb103535bec44da777e46b90df43a57 [diff] |
Merge "Fix signapk jar not found for prebuilt splits" am: f6f6c2f8cf Original change: https://android-review.googlesource.com/c/platform/build/+/2165007 Change-Id: I1ddf2a3db02c2a04440d6bd94b5aef4aea1f75fe Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.