How to import JNI to a project: Difference between revisions
| Line 2: | Line 2: | ||
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]]. | 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]]. | ||
=== Import so file === | === Import so file === | ||
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). | |||
The so files in API Demo are as follows: | |||
The so files in | |||
[[File:so files.png|frameless|left|thumb|caption]] | [[File:so files.png|frameless|left|thumb|caption]] | ||
=== Import JNI Interface file === | === Import JNI Interface file === | ||
Revision as of 12:08, 14 March 2020
How to import JNI
There are two steps to use JNI interfaces, one is to import so file, the other is to import JNI interface file.
Import so file
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). The so files in API Demo are as follows:
Import JNI Interface file
From the APIDemo, you can find the JNI interface generated by us, the package name of the JNI interface is defined in the so file, since you can not change the so file, so when copy the JNI interface, please notice that you can not change the package name of the JNI interface.
The JNI Interface class in APIDemo is like the follow picture, "com.cloudpos.jniinterface" is the package name, please don't change that name in your project.
