| commit | d5ed6019c9aa47d7aeebdf0ed8af4fa50870c755 | [log] [tgz] |
|---|---|---|
| author | Dario Freni <dariofreni@google.com> | Mon Dec 02 20:46:03 2019 +0000 |
| committer | Dario Freni <dariofreni@google.com> | Tue Dec 17 13:47:17 2019 +0000 |
| tree | d307edc5f5a58d18132a8aeae3a934519ebee94b | |
| parent | 4d5458d1f08cd8a8b34c53d462ad0292c97c96aa [diff] |
Move CtsShim and CtsPrivShim APKs out of system. These packages are now available in the shim apex package, which is made available in both flattened and unflattened apex configurations. Bug: 138429615 Test: atest CtsPrivilegedUpdateTests CtsPermissionTestCases CtsStagedInstallHostTestCases; (on both flattened and unflattened configurations) Merged-In: I03939f6c3e711d5887da201e32173f86a6b0289e Change-Id: I03939f6c3e711d5887da201e32173f86a6b0289e
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.