Both Java and Android developers access DIDKit through the Java bindings.
- DIDKit exposes a straightforward set of Java bindings, using the Java Native Interface (JNI).
- The JAR file includes all of DIDKit's Java class files. To use this in an
application, you must also include the shared library (
libdidkit.so) in your application in the Java library path
- For a quick function & type reference, you can study the DIDKitTest.java file.
- All the low-level calls that the Rust library exposes to JNI are documented in the JNI section of the Rust documentation.
Install Rust and DIDKit as usual and then:
To build the shared library for your current platform/architecture:
For Android, build the separate Android library (AAR file) which includes the Java class files and shared libraries for all Android targets.
Android Library (AAR file) for DIDKit. The AAR file includes Java class files using JNI, and binary shared libraries for Android's supported architectures (x86, armeabi-v7a, arm64-v8a, x86_64). The AAR can be added to existing Android projects using Android Studio or Gradle.
Android SDK and NDK for Linux x86_64. The Android SDK is expected to be installed at
~/Android/Sdk. If it is somewhere else instead, you can specify it with a Make variable, e.g.
Rust Android targets are also required. To install those with
ANDROID_SDK_ROOT- path to Android SDK. Default:
ANDROID_TOOLS- Android tools directory. Default is to pick one matching
ANDROID_NDK_HOME- Android NDK directory. Default is
$(ANDROID_SDK_ROOT)/ndk-bundle)if exists, or one matching
|Authentication, Tomcat, CHAPI||Github|
|Authentication, Maven, MySQL, Redis||Github|