| commit | ebbdea824f259eaa218fba6113f61b53a2ed627a | [log] [tgz] |
|---|---|---|
| author | bohu <bohu@google.com> | Sun Jun 10 00:11:30 2018 -0700 |
| committer | Po-Chien Hsueh <pchsueh@google.com> | Tue Aug 21 14:40:43 2018 +0800 |
| tree | 327c111a1b67dcf3840cb6bd1524b58dd0dfb476 | |
| parent | 5d1688bf27a8051cfdd5e2cc8c5d2b07cf79a9e8 [diff] |
emulator: factor vendor partition out of emulator.mk The emulator vendor paritions are better moved out of emulator.mk into device/generic/goldfish/vendor.mk so that changes in vendor.mk will just concentrate on vendor partition. this cl does not impact real devices, and it does not even impact emulator images (it does code refactoring only) BUG: 110030159 Change-Id: Ic5778cda8ca6ccf7bc2bc2f9028f801cda970143 Merged-In: Ic5778cda8ca6ccf7bc2bc2f9028f801cda970143 (cherry picked from commit 667685301600040c0006752bbf7ec0335efa9a56)
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.