commit | 666f85d0bce43f6a433b93efa387e7077cbd581a | [log] [tgz] |
---|---|---|
author | Treehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com> | Mon May 13 23:39:54 2024 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon May 13 23:39:54 2024 +0000 |
tree | 2a1976cdf6fa74bec6a5d16a51376cabacc4c40b | |
parent | 96dee8805b168840c3b85de7d50a034964945fa7 [diff] | |
parent | 3a0ab9ac43ac3e5ae02ea4ffb2ae35678bc5c449 [diff] |
Merge "Only consider EXTRA_INSTALL_ZIPS relevant by their primary file" into main am: a4b1e92ee0 am: 3a0ab9ac43 Original change: https://android-review.googlesource.com/c/platform/build/+/3083666 Change-Id: I1ad807bf20344af7da7327b8ca8cb9cc3042230f 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.