commit | d7dd3e2d3d3d3828b53a688f8cc965df1ba1b60c | [log] [tgz] |
---|---|---|
author | bohu <bohu@google.com> | Wed Jun 13 09:04:30 2018 -0700 |
committer | Bo Hu <bohu@google.com> | Wed Jun 13 22:10:51 2018 +0000 |
tree | 07e8a817198a67ffd14d693988276606e2c2d414 | |
parent | 941f8e102c024f884617baaa9471a27c55bdccb0 [diff] |
emualtor: cleanup media configuration The media configuration is handled by goldfish/vendor.mk already; clean them up from device.mk files. this cl does not impact arm devices; and it does the right thing for x86/64 devices because the media configuration should go to vendor instead of staying on system BUG: 110030159 Change-Id: If492f1e01f600b1c969e9ef04598f7af6783970e
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.