| commit | a32f00e553c1ffcd495b10d5b664e0744e53ac2c | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Mon Mar 18 14:23:15 2019 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Wed Mar 20 06:56:20 2019 +0900 |
| tree | 48300f40aa426929efef667053aa5072442ff797 | |
| parent | 0573298a182fc673cfee1c89e183b515c5383d0d [diff] |
Add LOCAL_SOONG_SYMBOL_PATH The soong-only variable is used to specify the location where the symbol file is located. When unspecified, LOCAL_MODULE_PATH is used instead as before. This is needed when the path that a file is installed to is different from the path that the file is accessed from at runtime. For example, if TARGET_FLATTEN_APEX=true, a file lib/libX.so in an APEX com.android.foo is installed to /system/apex/com.android.foo/lib/libX.so. However, it's runtime path is /apex/com.android.foo/lib/libX.so as /system/apex/com.android.foo is bind-mounted to /apex/com,android.foo. Bug: 120846816 Test: m and inspect that symbol files exist under $(PRODUCT_OUT)/symbols/apex/com.android.runtime/ Change-Id: I1b39f6e0cde115d442f14380c365796feff3437b
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.