How to import JNI to a project: Difference between revisions
Line 2: | Line 2: | ||
There are two steps to use the JNIInterface, one is to [[#Import so file|import the so file]], the other is to [[#Import JNI Interface file|import the corresponding JNI Inteface]]. | There are two steps to use the JNIInterface, one is to [[#Import so file|import the so file]], the other is to [[#Import JNI Interface file|import the corresponding JNI Inteface]]. | ||
=== Import so file === | === Import so file === | ||
From latest APIDemo, you can | From latest APIDemo, you can compile the neweast so files of all the devices in the POS. Then select the so file you want to import to your project, put the so file to the path '''lib/armeabi''', and '''lib/armeabi-v7a'''(for a special POS, the WizarPAD, the path is '''lib/mips'''), . | ||
The so files in APIDemo is like: | The so files in APIDemo is like: | ||
[[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 08:10, 11 January 2019
How to import JNI
There are two steps to use the JNIInterface, one is to import the so file, the other is to import the corresponding JNI Inteface.
Import so file
From latest APIDemo, you can compile the neweast so files of all the devices in the POS. Then select the so file you want to import to your project, put the so file to the path lib/armeabi, and lib/armeabi-v7a(for a special POS, the WizarPAD, the path is lib/mips), .
The so files in APIDemo is like:
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.