JavaCPP VS wasmer-java

JavaCPP and presets for working with JNI

In the meantime you might want to check out JavaCPP: https://github.com/bytedeco/javacpp

Maybe you can use JavaCPP?

Here is the code for JNI, which uses the prebuilt JavaCPP library to call the getpid function. We don't have to write all the manual C binding code and rituals as the JavaCPP library already does it.

Javacpp is the best ffi library of all https://github.com/bytedeco/javacpp

As for our approach, we maintain a library called javacpp: https://github.com/bytedeco/javacpp which proves a python wheel like experience where we distribute natively optimized c/c++ code (and even cuda accelerated code) as jar files on maven central. We also are able to develop with a python like experience by passing pointers around and other low level constructs directly allowing optimizations that you typically only get in c/c++.

https://github.com/bytedeco/javacpp

* it maps naturally and efficiently many common features afforded by the C++ language and often considered problematic, including overloaded operators, class and function templates, callbacks through function pointers, function objects (aka functors), virtual functions and member function pointers, nested struct definitions, variable length arguments, nested namespaces, large data structures containing arbitrary cycles, virtual and multiple inheritance, passing/returning by value/reference/string/vector, anonymous unions, bit fields, exceptions, destructors and shared or unique pointers (via either try-with-resources or garbage collection), and documentation comments*

I did not try myself, but for JNI maybe this could make lives easier? https://github.com/bytedeco/javacpp

Great idea! Luckily, there's https://github.com/wasmerio/wasmer-java, so you can easily run that wasm binary in your JVM running in your browser!

The biggest integration library is wasmer. It's intended as a server runtime for wasm. The official port wasmer-java has the problem of not supporting imports and that's also not to be implemented in the near future (they are restructuring the wasmer library according to this issue), the other is wasmer-jni. An inofficial jni-binding for the wasmer base implementation. Less nice to use, but feature complete.

Check how the rust compiler can target Web Assembly and then have a look at https://github.com/wasmerio/wasmer-java

If your savvy with WASM I think you could compile to wasm and make java bindings with https://github.com/wasmerio/wasmer-java