commit | 420cbba314a22a25f1e7d592c570773ce804b4d8 | [log] [tgz] |
---|---|---|
author | Treehugger Robot <treehugger-gerrit@google.com> | Tue Oct 19 20:33:52 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Oct 19 20:33:52 2021 +0000 |
tree | bc6d93398e68f459ba004db8d311f0aefb493a6b | |
parent | 7b8f295e4c2eeeafe881207e86eeecd4af4fb748 [diff] | |
parent | 11550760be0b2236fe224af363c6b32fc40109b9 [diff] |
Merge "A tool to facilitate large ninja files comparison." am: 3bd9c7d36a am: 8d9795f4d8 am: 6b7398bed0 am: 7588b06831 am: 11550760be Original change: https://android-review.googlesource.com/c/platform/build/+/1842085 Change-Id: I6818ac02b5365ddc73c64443d02d569951b8a3c0
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.