ndk-samples VS JavaCPP

https://developer.android.com/ndk. Java/Kotlin for the rest.

Best you can do is refer to the official samples and learn by taking one of the samples and modifying it to your use case. The comments in the samples should be quite adequate.

You can compile c++ for android using the NDK.

Mobile has a lot of C++ as libraries but in https://developer.android.com/ndk for android.

Then please provide references that say how to do this. Here https://developer.android.com/ndk it says:

cinterop is only for Kotlin/Native, where the whole application gets compiled to native code. If the target is Android, you want to use Native Development Kit (https://developer.android.com/ndk) instead.

It's a little convoluted since the app does still fork from the zygote with ART in there, but they added an entire layer of APIs so you can jump right in from C++. Here's a sample https://github.com/android/ndk-samples/blob/master/native-ac...

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