| commit | d203e12f20b5b7dc843f4c910739b2c21e5e8667 | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Thu Sep 01 23:24:47 2022 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Wed Sep 07 17:35:29 2022 +0000 |
| tree | 3a7b5ca2e4e51f873f0394e5d8f8f0bcade50f5b | |
| parent | 2a9b910bf4858343247b08e7554801ae43dbee79 [diff] |
Create partition-specific symlink for jnilib install Context - Currently, unembedded JNI libraries are being installed from a symlink based on an android_app's partition. - Unembedded JNI library may exist in a different partition from that of the app module, thus create a symlink based on the partition of each jni libraries. - Scope of this change is limited to bp modules, and does not affect mk modules. Implementation - Use the JNI library name:partition mapping from LOCAL_SOONG_JNI_LIBS_PARTITION_<target> to create a symlink. Bug: 154162945 Test: m Change-Id: Ie9396e0eb1c5bfc5855a2a84db395a2b9008b17b
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.