commit | 49e6f615a660cc30a063ad67e999f00743635270 | [log] [tgz] |
---|---|---|
author | Bill Yi <byi@google.com> | Tue Jul 11 15:35:47 2023 -0700 |
committer | Bill Yi <byi@google.com> | Tue Jul 11 15:35:47 2023 -0700 |
tree | 30da77eb6ae2f098a1cb525d8105fafd873a33b6 | |
parent | 6bd2bd8ae593bca2e054c883efe8ecc2666b9f02 [diff] | |
parent | d977883c39eff80be0830319484d0492b16b87e4 [diff] |
Merge TQ3A.230705.001 to aosp-main - DO NOT MERGE Merged-In: Ib0eee7237c81e43fe55da0c8569752e956891730 Merged-In: I1e276e220afe3c0c174a9822b0dce2a923be7b5c Merged-In: I8c8a4079974ee9e1009483350ab24f790471da9e Change-Id: I3b31eb8f5c003cb3fc7766e0a8d3378747304943
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.