-
Notifications
You must be signed in to change notification settings - Fork 72
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
Native part loading and missing library #12
Comments
Thanks for the update. If you're able to offer up a pull request containing these changes it'll help speed things up (I'm maxed out on other work at the moment). |
I am sorry... my git knowledge is almost non-existant... I can send you link to correct file.. here it is... You will probably need to modify it a little... |
No worries, thanks for the link. |
I'm not sure of the purpose of the native library loading since JNA already provides this with In the meantime I've added the Linux support for AMD64. |
It's simply for loading native library from jar file... so that you don't need to worry if user has correct file installed. When app is started and library loaded, correct native part will be loaded from jar and you can run with it... |
Is that still within scope of hid4java? If I understand you correctly it should be the case that JNA will load the correct hidapi library from the JAR through This mechanism would also be available for any other libraries a user may wish to load since JNA would be available on the downstream application's classpath and thus any other binaries they supplied should be accessible. Can you give me a use case where this is necessary? |
In order to progress the 0.3.0 release I'll close this issue and if it's still required then a new issue covering it specifically can be raised. |
You need to add class for loading native parts from jar... Project nrjavaserial uses something similar and it work great...
Library for linux x64 is missing at least one version of it, you need to create linux-amd64 directory and copy from linux-x86-64 (leave that one here).
The text was updated successfully, but these errors were encountered: