| commit | be371e1656c5d9ed8695c11935c5b900d8070367 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Thu Jun 14 16:39:04 2018 +0100 |
| committer | Anton Hansson <hansson@google.com> | Thu Jun 14 16:39:17 2018 +0100 |
| tree | 57e5c10e0d5d189ccaac623d254dab7a51984c87 | |
| parent | 2b0ea222c1e4118cf228ca75281ea68f2d74f29c [diff] |
Move a few packages from core_minimal.mk to base.mk.
All the products that inherit from base.mk add these packages, so moving
them up the hierarchy eliminates some duplication.
DownloadProvider
idmap
libneuralnetworks
mdnsd
MediaProvider
Bug: 80410283
Test: diff all product variables with multiproduct_kati
Change-Id: I133a385b3bc64261d73f616c416f7a905675c09d
Merged-In: I133a385b3bc64261d73f616c416f7a905675c09d
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.