diff options
| author | 2019-08-21 16:37:04 -0700 | |
|---|---|---|
| committer | 2019-08-28 11:02:26 -0700 | |
| commit | 9276cf0226d341927d0a7e682a8db677e25ae5dd (patch) | |
| tree | f90d1c8c1be0d2aaa38b58d9516f4e8dd529536d /tools/warn/cpp_warn_patterns.py | |
| parent | ccb86fe7d47b01ce06a968c0d2bc8d4024b8b8a6 (diff) | |
Check VINTF compatibility at OTA generation time.
Instead of relying on META/{system,vendor}_{manifest,matrix}.xml
and blindly copy compatibility.zip from target files package to
OTA package, do a static check on the input target files package
before generating the OTA package.
META/{system,vendor}_{manifest,matrix} does not contain ODM manifest
fragments, which is incorrect.
Also, the on-device check of compatibility.zip uses a old libvintf
binary on the device, which may not understand the incoming VINTF
metadata. This change removes the on-device check. Hence, it removes
the requirement of forwards compatibility of libvintf.
This behavior can be skipped with --skip-compatibility-check.
Test: build OTA package
Bug: 139300422
Bug: 131425279
Change-Id: I7fb93be9eb73f578fc05a182c6c9d1f073db2800
Diffstat (limited to 'tools/warn/cpp_warn_patterns.py')
0 files changed, 0 insertions, 0 deletions