Lines Matching refs:of

11 The most typical use case of this library is calling `System.loadLibrary(name)`.
16 from the namespace. The actual searching, loading, and linking of the library
22 from the namespace, thus preventing an APK from loading JNI libraries of other
26 characteristics of the APK such as whether or not the APK is bundled with the
27 platform. In case of the unbundled, i.e., downloaded or updated APK, only the
29 are available from the platform, whereas in case of the bundled, all libraries
39 The list of public native libraries is not static. The default set of libraries
54 Lastly, libnativeloader is responsible for abstracting the two types of the
61 Implementation wise, libnativeloader consists of four parts:
68 `native_loader.cpp` implements the public interface of this library. It is just
77 models a linker namespace. Its main job is to abstract the two types of the
78 dynamic linker interface so that other parts of this library do not have to know
79 the differences of the interfaces.
82 native libraries from the various partitions. It can be considered as a part of
83 `LibraryNamespaces` but is separated from it to hide the details of the parsing