Victor Gaydov

You're welcome

> regarding libroc.so can we set LDFLAGS=-static-libstdc++ before compiling with scons or do you have a different approach? I didn't try it yet. If LDFLAGS will work well, let's start...

> For libroc_jni.so, we can actually don't use C++. It seems that most files can be just renamed from .cpp to .c. It seems that the only C++ feature we're...

I guess we'll have to publish both jar and aar.

One important question to think about. When we're creating AAR, we include prebuilt libroc.so and libroc_jni.so for all 4 supported Android ABIs. What should we do in case of JAR?...

BTW, in Go bindings we don't ship any native libraries and require system-wide installation of libroc.so. But in Go bindings we also don't need a native bridge like libroc_jni.so. AFAIK,...

> In case of JAR in my opinion we should only ship libroc_jni.so library for differents os/architectures and let user pre-install libroc. Another thought, what about libc? Should we also...

BTW, are there any cases where a JAR *without* libroc_jni is useful (assuming that libroc doesn't provide libroc_jni too). Also, a stupid question. Is there a way to create and...

I'm now thinking about the following solution: * Select the list of hardware architectures we want to support. * Select the list of operating systems and their versions we want...

It seems that rocksdb uses a similar approach: https://github.com/facebook/rocksdb/pull/3143. It would be helpful to find out how other projects deal with this problem.