Java and Android
both Java and Android developers access DIDKit through the Java bindings
Last updated
Was this helpful?
both Java and Android developers access DIDKit through the Java bindings
Last updated
Was this helpful?
DIDKit exposes a straightforward set of Java bindings, using the Java Native Interface ().
The 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 .
Install Rust and DIDKit as usual and then:
Run:
To build the shared library for your current platform/architecture:
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. make ANDROID_SDK_ROOT=/other/location/android-sdk.
Rust Android targets are also required. To install those with rustup, run:
Make variables
ANDROID_SDK_ROOT - path to Android SDK. Default: ~/Android/Sdk
ANDROID_TOOLS - Android tools directory. Default is to pick one matching $(ANDROID_SDK_ROOT)/build-tools/*.
ANDROID_NDK_HOME - Android NDK directory. Default is $(ANDROID_SDK_ROOT)/ndk-bundle) if exists, or one matching $(ANDROID_SDK_ROOT)/ndk/*.
Authentication, Tomcat, CHAPI
Authentication, Maven, MySQL, Redis
For Android, build the separate which includes the Java class files and shared libraries for all Android targets.
for DIDKit. The AAR file includes Java class files using , 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.