How to import JNI to a project: Difference between revisions

Latest revision as of 08:11, 10 January 2024

Import .so File

Compilation: First, compile the latest .so files from the latest API Demo for POS devices.
Selection and Placement:
- For standard devices, import and place these files in the lib/armeabi and lib/armeabi-v7a directories.
- For specific models like WizarPad, place them in the lib/mips directory.
API Demo Reference: The API Demo includes the following .so files:

Import JNI Interface File

The JNI interfaces generated for smart POS applications can be found in the API Demo. It's important to note a few key guidelines:

Package Name Consistency: The package name for the JNI interfaces is predefined in the .so file.
- Important: Do not modify the package name when copying the JNI interface.
- Example: If the package name is "com.cloudpos.jniinterface," ensure it remains unchanged in your project.

List of JNI Interface Classes: The API Demo includes the following JNI interface classes:

A visual representation of the JNI interface classes can be helpful. The below image shows the JNI interface classes as found in the API Demo.

@@ Line 1: / Line 1: @@
-== How to import JNI ==
+=== Import .so File ===
-There are two steps to use JNI interfaces, one is to [[#Import so file|import so file]], the other is to [[#Import JNI Interface file|import JNI interface file]].
+* '''Compilation''': First, compile the latest .so files from the latest API Demo for POS devices.
-=== Import so file ===
+* '''Selection and Placement''':
-You can compile the latest so files of POS devices from the latest API Demo, then select the so files to import into the project, and put them in the path of lib/armeabi and lib/armeabi-v7a (for special POS such as wizarpad, the path is lib/mips).
+** For standard devices, import and place these files in the '''lib/armeabi''' and '''lib/armeabi-v7a''' directories.
+** For specific models like WizarPad, place them in the '''lib/mips''' directory.
+* '''API Demo Reference''': The API Demo includes the following .so files:
+[[File:so files.png|frameless|left|thumb|caption]]
-The so files in API Demo are as follows:
-[[File:so files.png|frameless|left|thumb|caption]]
-=== Import JNI Interface file ===
-The JNI interfaces we generated can be found in API Demo. Please note that their package name is defined in so file and cannot be modified. When copying JNI interface, please do not change the package name of JNI interface. For example, "com.cloudpos.jniinterface" is the package name, please do not change it in the project.
-The JNI interface classes in API Demo are as follows:
+=== Import JNI Interface File ===
+The JNI interfaces generated for smart POS applications can be found in the API Demo. It's important to note a few key guidelines:
+* '''Package Name Consistency''': The package name for the JNI interfaces is predefined in the .so file.
+** '''Important''': Do not modify the package name when copying the JNI interface.
+** '''Example''': If the package name is "com.cloudpos.jniinterface," ensure it remains unchanged in your project.
+* '''List of JNI Interface Classes''': The API Demo includes the following JNI interface classes:
+A visual representation of the JNI interface classes can be helpful. The below image shows the JNI interface classes as found in the API Demo.''
 [[File:jniinterface.png|frameless|left|thumb|caption]]