| commit | b321665b9da4884560ea266908ed50516b33c630 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Wed Feb 13 16:32:40 2019 -0800 |
| committer | Yifan Hong <elsk@google.com> | Tue Feb 19 12:37:50 2019 -0800 |
| tree | 36f2f867835da9db4694e3b672cd46466e4e94c8 | |
| parent | da4ee462c72b7ebeac7aaf0142986caa5fc1fc0a [diff] |
Build ODM manifests and fragments for each SKU.
In BoardConfig.mk, ODM manifests can be specify as follows:
# installed to /odm/etc/vintf/manifest.xml
ODM_MANIFEST_FILES := device/foo/bar/odm_manifest.xml
# installed to /odm/etc/vintf/manifest_baz.xml
ODM_MANIFEST_SKUS := baz
ODM_MANIFEST_BAZ_FILES := device/foo/bar/odm_manifest_baz.xml
This is preferred over PRODUCT_COPY_FILES because it uses
assemble_vintf to check manifest at build time.
Test: builds
Change-Id: I18517b8ba09d3271627d6f21b8250b1bfc9e5db3
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.