| commit | 3387e656861ebfaea8a1216674965ba13dcbbad3 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Sun Dec 16 11:02:09 2018 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Fri Jan 11 13:33:56 2019 +0900 |
| tree | 89611aee9a41056944448fabf77fd3171654202c | |
| parent | bdf0ec03b67f044fa9f9d1a5ab488b0fe96445b5 [diff] |
Add $(PRODUCT_OUT)/apex to the artifact path whitelist $(PRODUCT_OUT)/apex is where shared libraries in APEXes get installed into. The path can be considered as a fake path as the shared libraries are installed there just to have symbol files for them under $(PRODUCT_OUT)/symbols/apex for debugging purpose. Shared libraries in APEXes are made available to the path at runtime by mounting APEXes via apexd. The files under $(PRODUCT_OUT)/apex are never compiled into a file system image (e.g. system.img) Bug: 120846816 Test: build/soong/build_test.bash -dist -products mainline_system_arm64 Change-Id: I3727091214f08f945559fa5f0f1450e74c1a5c9b
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.