commit | 736b223d5f78f6abdf1af7aae4742900395f9ec4 | [log] [tgz] |
---|---|---|
author | Bill Peckham <bpeckham@google.com> | Mon May 06 12:50:55 2019 -0700 |
committer | Bill Peckham <bpeckham@google.com> | Mon May 06 23:23:23 2019 +0000 |
tree | a3106dd97eeb0bec39eea26d3328faf4024c2985 | |
parent | 5e25df9f5a1a2ab8dc84f5088517507f1c5a3980 [diff] |
Use file_contexts.bin from other build to regenerate images. The old process_file_contexts_bin function did not properly generate a usable file_contexts.bin to regenerate images, so instead use the file_contexts.bin from the other partial target files package. When combining any one of several other partial target files packages with a single system partial target files package, this file will properly apply contexts as long as the same source is used for the system partial target files. Test: Verify that file contexts are properlty applied to vendor image. Bug: 131584454 Change-Id: I16f8cc3b7f2eb7f09746f0ddcb2c1daf3fd19da6
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.