| commit | 3629aa77da21827d4e6d04464cdc04b2cef2e36d | [log] [tgz] |
|---|---|---|
| author | Steven Moreland <smoreland@google.com> | Wed Apr 04 15:41:05 2018 -0700 |
| committer | Steven Moreland <smoreland@google.com> | Thu Apr 05 11:26:35 2018 -0700 |
| tree | 0865768db978f3d77ccce6537a13cff536b098db | |
| parent | c22e207c501f3ee4bf903a5bcd542a1a674f357d [diff] |
Support manifest fragments. LOCAL_VINTF_FRAGMENTS/vintf_fragments are used to specify what manifest fragments should be installed by a target. Test: fragments get installed to the right location Test: broken fragment gets detected Test: boot device and verify service is working and manifest is updated Test: verify OTA package contains fragments Bug: 66917623 Change-Id: I21abe65a31b8c3d255c8ccd80e102ff3acb23105
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.