| commit | c3f1356a3a70a1cbcbe7853ea19a83dc451a0633 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Mon Mar 19 18:12:39 2018 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Fri Mar 30 10:12:30 2018 +0900 |
| tree | 9b928614bf239d4304468cb5d7b1168dd5876bc9 | |
| parent | a143397aee50d21c74c8fe06c651a0abfc785295 [diff] |
Allow platform modules to link to vendor public libraries Normally, when building with VNDK, platform modules are not allowed to link against vendor libraries, because the ABI of the vendor libraries are not guaranteed to be stable and may differ across multiple vendor images. However, the vendor public libraries are the exceptions. Vendor public libraries are vendor libraries that are exposed to 3rd party apps and listed in /vendor/etc/public.libraries.txt. Since they are intended to be exposed to public, their ABI stability is guaranteed (by definition, though it is up to the vendor to actually guarantee it). This change allows platform modules to link to vendor public libraries. When the name of a vendor public libraries (whose stub is defined via vendor_public_library in Android.bp) is listed in LOCAL_SHARED_LIBRARIES, it is actually linked to the stub library which is available to platform modules. Bug: 74275385 Test: m -j Change-Id: I063b43431196190b59332b1bcad59f267073f89f
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.