commit | 52e5c1094e941e72a1008f124315b07a3038d4c6 | [log] [tgz] |
---|---|---|
author | Ricardo Cerqueira <ricardo@cyngn.com> | Tue Feb 10 23:58:10 2015 +0000 |
committer | Jackeagle <jackeagle102@gmail.com> | Thu Aug 09 12:54:01 2018 -0400 |
tree | 8c442006e23f7a8f873d848e2441180338ee0af4 | |
parent | 7325c5e2c2066485c7fd0cf55cf422c3bc38d95c [diff] |
Revert "Add handheld_core_hardware.xml to telephony base" Don't do this. handheld_core_hardware.xml includes feature declarations that aren't mandatory, particularly cameras and magnetometers, but also things like managed users. According to the CDD, these are optional. Go back to the pre-L mechanism of including the declarations per-device to make them accurate. This reverts commit dccce7bbe9673d4b8ce1a3559182767f926e1ff8. Change-Id: I6db55082295171b78fe595e783799ee54458c4fd
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.