Skip to content

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

@jasonsparc

Description

@jasonsparc

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions