| commit | 0118b91e95a79cd94f9f62797ce322f017f15609 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Feb 03 18:03:43 2023 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Feb 03 18:03:43 2023 +0000 |
| tree | 5038529b51b583a64c4edc91cd491957627abfe6 | |
| parent | 690b21efd28f12cf3079c8df77f72eca4d73f7dd [diff] | |
| parent | 7e559f9c245f3d5b94b3be4078618db7403e6714 [diff] |
Snap for 9560500 from 7e559f9c245f3d5b94b3be4078618db7403e6714 to sdk-release Change-Id: Ifdd7241a1f0d5399a0cc62bd77501634d86b5a4c
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.