| commit | b27c2e8af953bf78701b6f0a8c07db070f4e9e68 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Wed Sep 23 19:15:20 2020 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Wed Sep 23 15:43:58 2020 +0000 |
| tree | 9e90a5a54b7abb779dbae578f50113cfc4bd2eb2 | |
| parent | 08ba15ef3299890c9407dee2f05bb8032d49a60a [diff] |
Use file_contexts for flattened apexes
Because flattened apexes are installed in /<partition>/apex, associated
file_contexts file should be modified to accommodate path changes and
also merged into target-wide file_contexts.bin file.
Soong now emits modified file_contexts via LOCAL_FILE_CONTEXTS, and
these files are collected into a temporary file_contexts.modules.tmp
file, which is used as an additional input of file_contexts.bin.
Bug: 166518492
Test: m file_contexts.bin
check the contents of file_contexts.concat.tmp file
Change-Id: I002a2294af9e06baeaf54bc5a9a5380d23b8a3da
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.