commit | 0a0c4dc6aa601947102f843ad157f5c9a2786d34 | [log] [tgz] |
---|---|---|
author | Anton Hansson <hansson@google.com> | Thu Jun 14 03:44:53 2018 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Thu Jun 14 03:44:53 2018 -0700 |
tree | ba58bd4159a0efbd3e31f57cd8bd5c5388c15123 | |
parent | 165f17dc0519e36cc9c4d2d5aa5879ec4a376fb4 [diff] | |
parent | 727e5d9f5935bfae925790182496e1311a601a3b [diff] |
Merge "Add a new macro for products to make artifact path requirements." am: 2b0ea222c1 am: 727e5d9f59 Change-Id: I9a8106d3832ba7f885b4b1b1dbe24a1c9b566647
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.