Lines Matching refs:library

6 shared library, without changing the Android framework.  It also shows how to
7 write JNI code for incorporating native code into the library, and a client
8 application that uses the library.
12 a custom library as shown here.  It can not be used to create a third party
13 shared library, which is not currently supported in Android.
15 To declare your library to the framework, you must place a file with a .xml
20     <library name="com.example.android.platform_library"
31 The top-level Android.mk defines the rules to build the shared library itself,
33 library lives under java/.
35 Note that the product for this library is a raw .jar file, NOT a .apk, which
36 means there is no manifest or resources associated with the library.
37 Unfortunately this means that if you need any resources for the library, such
44 Other than that, the library is very straight-forward, and you can write
46 namespaces -- the namespace given in the <library> tag above is just the
47 public unique name by which clients will link to your library, but once this
48 link happens all of the Java namespaces in that library will be available
56 shared library.  This code lives under jni/.  The jni/Android.mk file defines
58 provides everything needed to hook up the native code with the Java library
66 shared library.  This code lives under client/.  Note that the example is
68 build system.  The only two special things needed to use your library are:
71 against your shared library.
73 - A <uses-library> line in the AndroidManifest.xml to have the runtime load
74 your library into the application.