commit | 64b824d3c1709075e53c7219ad47cb94ca43f946 | [log] [tgz] |
---|---|---|
author | Yifan Hong <elsk@google.com> | Thu Jan 11 19:28:38 2018 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Thu Jan 11 19:28:38 2018 +0000 |
tree | 9e2418c56906b124ae14ecf38e3eae8ee26509d2 | |
parent | 11f9f969137bef7f936d88a07f7f2f579912f2cb [diff] | |
parent | 1017eaa38c6d35d80ca220ba5e6562ee15943182 [diff] |
Merge "framework_cm.xml: move to hardware/interfaces" am: 1e7ab9db8f am: 32faacadf0 am: 1017eaa38c Change-Id: I17fdf26b20fcaad58f5d6170e59450d23ae92804
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.