| commit | 5a4593c9d7f663b69e488b929c4dfbdfadbb0366 | [log] [tgz] |
|---|---|---|
| author | Jeff Sharkey <jsharkey@android.com> | Thu Nov 21 15:57:09 2019 -0700 |
| committer | Jeff Sharkey <jsharkey@android.com> | Thu Dec 05 10:08:56 2019 -0700 |
| tree | 11765f1cfd0c22cf06cef04778b4ed291bee07d4 | |
| parent | 876252ff1dfef935b67f4b1e9b5623cf1efe7412 [diff] |
Structure MediaProvider as an APEX. Based on guidance from the Mainline team, we're placing the MediaProvider APK inside a new APEX, as this will allow us to move MediaStore.java inside the module boundary in a future CL. As part of this restructuring, we need the pre-Mainline APK to remain intact to preserve the user's media database. There is already logic in place from previous CLs that will migrate data from the pre-Mainline to the post-Mainline world, including tests to verify that the migration works. Bug: 144247087 Test: atest --test-mapping packages/providers/MediaProvider Change-Id: I571eccbb2950a7c518a682eae3350ba7ef9bd804
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.