-
Notifications
You must be signed in to change notification settings - Fork 39
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
Embed Dynamic Libraries for Different Operating System [2 XMR] #12
Comments
That would be great. I welcome any outside help. |
There is a bounty on this issue. The amount is in the title. The reward will be awarded to the first person or group of people who resolve this issue. If you are starting to work on this bounty, please write a comment so that we can assign the issue to you. We expect contributors to provide a PR in a reasonable timeframe or, in case of an extensive work, updates on their progress. We will unassign the issue if we feel the assignee is not responsive or has abandoned the task. Read the full conditions and details of the bounty system. |
Bounty added to package the native libraries into the JAR which is portable across platforms. The native libraries can be downloaded from the latest release. |
This issue is resolved in the latest release, so the native libraries are now distributed with the JAR file, and clients do not need to build them. Thanks for the request almost 5 years ago! :) |
It's worth investigating how one might build the dynamic library for different platforms and distribute that through Maven. Projects like lmdbjava and native platform all include significant native libraries but this is transparent to Java applications which need only declare dependencies on the Maven artifacts. Ideally, I think, there would be separate projects to build the publish the native library to Maven. Developers could use pre-built artifacts in Maven central or build their own. All these would then get sucked into the classpath by the core monero-java dependency and at runtime, depending on the OS, the right library would be loaded.
The text was updated successfully, but these errors were encountered: