Jiyong Park b07885714c Rename non-stubs variant of a lib if it is included in APEX ... If a lib is directly included in an APEX (via native_shared_libs property) and the lib has stubs (via stubs.versions property), then the ordinary non-stubs variant of the library is renamed to <libname>.bootstrap in the makefile. At the same time, the stubs variant of the lib becomes visible and it's name is <libname>. This ensures that modules in Android.mk build against the stubs variant thus preventing them from using private APIs in the lib. The non-stubs variant, however, is used if the module explicitly has set the new 'bootstrap' property to true. This is useful for building some early binaries (such as init and vold) which need to run before APEXes are activated. Since they can't use the bionic libs from the runtime APEX, they should use the bionic libs left in the system partition which is called the boostrap bionic. Bug: 120266448 Test: m Test: m with https://android-review.googlesource.com/c/platform/bionic/+/849044 Change-Id: I882b8aeb5b29460f07b4424e4f8eb844d6c9a9b0		2019-01-10 09:57:29 +09:00
..
apex.go	Rename non-stubs variant of a lib if it is included in APEX	2019-01-10 09:57:29 +09:00
apex_test.go	Rename non-stubs variant of a lib if it is included in APEX	2019-01-10 09:57:29 +09:00
key.go	Add installable property to apex_key	2019-01-04 03:23:12 +09:00