commit | 5fa6bc05a504ccd9b179d28edc583a81fa3eaca4 | [log] [tgz] |
---|---|---|
author | Treehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com> | Wed Dec 20 18:45:34 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Dec 20 18:45:34 2023 +0000 |
tree | ee4371673d60cbe8ec60d5f408bed38d93bc8cb0 | |
parent | 940124085408df0b6899d5671ac1e6b2a9b457d0 [diff] | |
parent | 2014c8fefe7e223653be73103c465146b84790c0 [diff] |
Merge changes Id392a33c,Iabf8875f into main am: e1cd8461a3 am: d74d671c20 am: 2014c8fefe Original change: https://android-review.googlesource.com/c/platform/build/+/2883080 Change-Id: I5eeb4f91700a0916da8911c73633fcda1034c839 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.