| commit | 62d51b65aab0fb52fee79a4e4ea71708e8fb7f71 | [log] [tgz] |
|---|---|---|
| author | Tri Vo <trong@google.com> | Tue Feb 19 11:23:12 2019 -0800 |
| committer | Tri Vo <trong@google.com> | Tue Feb 19 18:32:55 2019 -0800 |
| tree | 6319d3daf7a543482b8e1a09d47b1fd3df39c597 | |
| parent | dd025116cd076c78d90b82c003379805317da295 [diff] |
recovery: install product_file_contexts and product_property_contexts Product partition is not mounted in recovery mode. Install product_file_contexts and product_property_contexts into rootdir for recovery. This is similar to how we deal with system, vendor, and odm *_contexts files. And remove unnecessary ifdefs. Test: m bootimage for pixel 3, product_file_contexts and product_property_contexts appear in $OUT/recovery/root/ Change-Id: I416d9e6ea742e67a6fe294f1ad8b78fb9b844260
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.