| commit | e3ba82cff24a2bf44c39230cf1f6d934c3f4c644 | [log] [tgz] |
|---|---|---|
| author | Yifan Hong <elsk@google.com> | Wed Aug 21 13:29:30 2019 -0700 |
| committer | Yifan Hong <elsk@google.com> | Wed Aug 28 11:02:26 2019 -0700 |
| tree | bad1470f904d1d58285a84f33e09c80512ee9e0f | |
| parent | 33dfa52cdda70120075d9191e596ab32a7e73225 [diff] |
Add a script to check VINTF compat of target files package.
Instead of checking META/{system,vendor}_{manifest,matrix}.xml (which
is error-prone because ODM SKU-specific manifests are not checked),
this script read the target files package, remaps its directory
structure so that checkvintf understands it, and check VINTF
compatibility.
Also, put it in otatools.zip.
Test: run it on an extracted target files package
Bug: 131425279
Change-Id: I06036f9a8d7242d4bc11524028be40e780c508e8
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.