SWIG VS JavaCPP

How is this any different than a mature tool such as SWIG (https://www.swig.org/)?

I've used SWIG extensively with Python to call C code and import C headers for testing/tooling purposes.

For pure C, CGO. For C++ they are likely creating shims with Swig: https://www.swig.org/

I mostly write in C and C++ so for language bindings I use Swig a lot. Say Im creating a machine learning library in C++, its very easy to create a Python API that can call the C++ classes and methods using Swig. iirc, I am using the same swig interface file to create bindings for Python, OCaml, R and even Fortran. Feel free to DM me if you got any more questions or anything!

Swig can make c++ types and functions available to python.

The likes of SWIG is often used to link C library-like code to 11-ish other widely used languages.

Maybe you could use swig to create a wrapper for Java.

But, you might find these links interesting: * https://github.com/swig/swig/issues/918 * https://github.com/kaby76/swigged.llvm

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