commit | 646de99112eb384362a381ad940feeb6b60aa1c3 | [log] [tgz] |
---|---|---|
author | Nikita Ioffe <ioffe@google.com> | Thu Feb 15 20:07:01 2024 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Feb 15 20:07:01 2024 +0000 |
tree | 25ab4f729041f8c90bf41dcd2911227bc537b636 | |
parent | 0d8443fd599bcf4d854768f2838f6c8ae3e50780 [diff] | |
parent | 01767ec382be335299d918c48b88d69500938bce [diff] |
Merge "Propagate RELEASE_AVF_MICRODROID_KERNEL_VERSION to Soong" into main am: 01767ec382 Original change: https://android-review.googlesource.com/c/platform/build/+/2962202 Change-Id: I0bfd4ba97f41dfdd5e5eceb30381d71ff968a461 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.