We want to move to JNI for performance reasons, and it also clarifies the confusion that the dual license situation of JNA might create. We're using it as apache 2, but not all tools (including maven meta-data) support dual-licenses and this could cause down-stream confusions which we rather avoid.
For JNI we will need to setup cross compilation, some places where this is discussed:
We'll only need to add support for JNI for macOS, and then mainly for x64 and arm64.
We want to move to JNI for performance reasons, and it also clarifies the confusion that the dual license situation of JNA might create. We're using it as apache 2, but not all tools (including maven meta-data) support dual-licenses and this could cause down-stream confusions which we rather avoid.
For JNI we will need to setup cross compilation, some places where this is discussed:
We'll only need to add support for JNI for macOS, and then mainly for x64 and arm64.