| commit | b14b530f829c73c157dff4def0a594f365895866 | [log] [tgz] |
|---|---|---|
| author | Steven Moreland <smoreland@google.com> | Wed Dec 20 10:44:10 2017 -0800 |
| committer | Steven Moreland <smoreland@google.com> | Fri Dec 22 14:02:11 2017 -0800 |
| tree | 18da1b92e477bdccc855922b3c582f7fa9759c0c | |
| parent | 98acb09033f00d6e4640c875b737f5ea5de98c5e [diff] |
Allow devices to extend the system manifest. Introduces DEVICE_FRAMEWORK_MANIFEST_FILE, a list of files which are added to system/manifest.xml. This is required for devices to properly display what hals they implement and also therefore for them to pass vts_treble_vintf_test since it now tests manifests based on hal origin. Notice, this is named singularly to match DEVICE_MANIFEST_FILE which is also a list of files. They may be better both named "FILES", but for consistency and legacy reasons, they can be thought of as "everything that composes the X manifest file". Fixes: 70042049 Test: add system manifest extension which needs it and it no longer fails vts_treble_vintf_test for hals being served from the wrong partitions. Change-Id: I1f59d5c3cadb7a7d4576b73196ca7b41103a49c5
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.