-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide Java package for deployment #106
Comments
The generated library file But there are few things to do:
|
How can a dedicated loader implemented in IRI internally? Can we reuse the codesnip taken from |
I will reference from the file of rocksDB: NativeLibraryLoader.java
|
Build with option `BUILD_JNI=1` would compile the Java code and create the JAR file. The dcurl shared library `libdcurl.so` would be packaged into the JAR file and can be extracted from it for Jave native interface easily. Close DLTcollab#106.
Build with option `BUILD_JNI=1` would compile the Java code and create the JAR file. The dcurl shared library `libdcurl.so` would be packaged into the JAR file and can be extracted from it for Jave native interface easily. Close DLTcollab#106.
Current JNI build process generates shared library in the form of pearldiver driver for IRI. However, it is not convenient for deployment as RocksDB does. By providing
rocksdbjni
package, maven can find and packagerocksdbjni
into final IRI jar file including RocksDB C++ library.Once we can provide similar java package (likely
dcurl-jni
), we can simplify the process of validation and deployment.The text was updated successfully, but these errors were encountered: