commit | 2e011580a5edb870ffe0d8c2918513c4f7aabf4a | [log] [tgz] |
---|---|---|
author | Treehugger Robot <treehugger-gerrit@google.com> | Fri Mar 11 00:48:42 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Mar 11 00:48:42 2022 +0000 |
tree | b977c44ebfef0f72f5c66573b3fc93f1594b3460 | |
parent | 1335f0010c1b121ffc4fa9bb551d7f73ad9d08c0 [diff] | |
parent | 567da60c58d3584c3084588d7caaf70381322063 [diff] |
Merge "Moves merge scripts into a new merge folder." am: 51005914bd am: 0d0abf6cbc am: 567da60c58 Original change: https://android-review.googlesource.com/c/platform/build/+/2006512 Change-Id: I4f787a582c506fadf683b99b73bc165194fb48b1
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.