commit | 0dc56e87583fce6c48a6700e9a5d38d2a3e2582f | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu May 18 22:23:24 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu May 18 22:23:24 2023 +0000 |
tree | d4d914dfbcc43af7b8d319abeebb1c93662518d1 | |
parent | 3a502767f12189fbbf1bbbd92d957d561709ac50 [diff] | |
parent | 1c98538eee038dabe877399259c7beee88c7d030 [diff] |
[coastguard skipped] Merge sparse cherrypicks from sparse-10161073-L49900000960778179 into tm-qpr3-release. COASTGUARD_SKIP: I2bb1848e16aff436787a5bf43dbea18012d485a7 COASTGUARD_SKIP: I9b94fecbdce0ed3fcfa5bb9674d890e1196a0fbe Change-Id: I39e3f07bfef31d1b2aac7c7f6532fbbb08d3ab98
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.