commit | adf5feeda27be5b51970549dc97cc08a0e054360 | [log] [tgz] |
---|---|---|
author | Treehugger Robot <treehugger-gerrit@google.com> | Wed Jan 12 01:41:09 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jan 12 01:41:09 2022 +0000 |
tree | fcaa949ed216cc12153994de86ba64354eb29916 | |
parent | 022e8e293ff83ec94200b0009304bb53a0b3bc62 [diff] | |
parent | 2e04c83b6befabad000df89259c9fe8428175aa3 [diff] |
Merge changes Ia2ec1b81,Ibc831ae8 am: 49380ebecf am: 5955f8a521 am: 4817ded07b am: 2e04c83b6b Original change: https://android-review.googlesource.com/c/platform/build/+/1941454 Change-Id: I54efe335ac9d3ceea817c176872249be701900f4
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.