commit | e1c7242588e4254b610141c91a1205a0467d74c2 | [log] [tgz] |
---|---|---|
author | Juan Yescas <jyescas@google.com> | Fri Oct 20 05:02:59 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Oct 20 05:02:59 2023 +0000 |
tree | 68889d51d68cc04602eec8e78e0c344adcc7ffa7 | |
parent | c143532ca346d00d2b0e595b5f248536ef67e5ae [diff] | |
parent | 82c92d01e051bae68ec40849812c877da1cac156 [diff] |
Merge "16k: Sign the APKs to support 4k/16k page sizes" into main am: 4d136f5265 am: e12c624460 am: 82c92d01e0 Original change: https://android-review.googlesource.com/c/platform/build/+/2786950 Change-Id: I3621aa1ff27cb01bc14bbb153c9b4445e961d96f 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.