Skip to content
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

Request: JNA-only and JNI-only published separately #39

Open
jasonsparc opened this issue Mar 12, 2023 · 0 comments
Open

Request: JNA-only and JNI-only published separately #39

jasonsparc opened this issue Mar 12, 2023 · 0 comments

Comments

@jasonsparc
Copy link

I know nothing about the underlying implementation (so feel free to correct my misinterpretation) but a quick glance tells me that there's both a JNA-only and JNI-only implementation, and that the user may freely choose between the two, but only one should be used at runtime.

If so, I believe it would be better if there are separate packages published that users could depend on: one for JNA-only, one for JNI-only, and one for both. Right now, the jar artifact contains both, so for example, even though I'm using only the JNA implementation, I also have the JNI binaries unnecessarily included and thus unused.

I'm using Gradle to include this library as a dependency, and there may be a way to transform the jar artifact, but it seems complicated to do so. It would really be great if the JNA and JNI implementations are available as separate modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant