| commit | d33515623ab66a9d7565176a5a0583b7056ab0cf | [log] [tgz] |
|---|---|---|
| author | Daniel Norman <danielnorman@google.com> | Thu Oct 29 12:33:11 2020 -0700 |
| committer | Daniel Norman <danielnorman@google.com> | Thu Nov 05 15:17:05 2020 -0800 |
| tree | 148624e3177b8f89d62a4d6f031ce52e403252c8 | |
| parent | b8d52a2fdcefc564b10229c22ba04b05c80eabac [diff] |
Checks for APK sharedUserIds that cross partition group boundaries.
This check is used when merging target files to ensure that a merged
build does not contain any APKs that share UID across builds.
Bug: 171431774
Test: test_common
Test: Use merge_target_files.py to merge two partial builds,
observe no failures for inputs without colliding APKs.
Test: Use merge_target_files.py to merge two partial builds,
observe failure for inputs that have an APK that shares a
UID across input partition groups.
Change-Id: I9dc57216882741ae46a99cfd7847f34702c75582
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.