| commit | 3f1c9577e821855513e63f970000ed2a3c9d9a59 | [log] [tgz] |
|---|---|---|
| author | Rob Seymour <rseymour@google.com> | Thu Jul 28 21:56:28 2022 +0000 |
| committer | Rob Seymour <rseymour@google.com> | Thu Sep 22 23:01:44 2022 +0000 |
| tree | 7b7bbd4c1f2d9a9d372eaf9ebdd875643c0a3663 | |
| parent | 2a9b910bf4858343247b08e7554801ae43dbee79 [diff] |
Add APEX data to checkvintf for compatibility check.
As part of extending libvintf to support VINTF data inside of APEXes:
Create apex-info-list.xml as part of build to pass into checkvintf.
Include the /apex data to dirmap
Extend check_target_files_vintf.py to include APEX data:
Unzip APEX from partions
Extract APEX data
Create apex-info-list.xml
Bug: 239055387
Bug: 242314000
Test: m
Test: m dist
Change-Id: I4b4e159051bacb46dc43b83e006ca0f0eb58d772
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.