commit | 806c2529538ba490e21b4bded3b91fca34b6bcf1 | [log] [tgz] |
---|---|---|
author | Treehugger Robot <treehugger-gerrit@google.com> | Wed Jan 12 04:32:54 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jan 12 04:32:54 2022 +0000 |
tree | d2e49aa1e91d125983eefea97f2d0d500aaa4139 | |
parent | 2e04c83b6befabad000df89259c9fe8428175aa3 [diff] | |
parent | 14e6ca5053011b8616c93c55f9a3f2636b4acf26 [diff] |
Merge "Updates OWNERS file" am: 35efbedb4f am: dd52cdce2e am: 14e6ca5053 Original change: https://android-review.googlesource.com/c/platform/build/+/1944687 Change-Id: I34fbfa9fe76da1688a6b680d80de8a2a3fae5bf5
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.