Matteo Arella

Great! A dev setup can be obtained running travis-ci jobs locally. ### Linux 1. build libroc: ``` scripts/travis/linux/before_install.sh scripts/travis/linux/install.sh ``` 2. build roc-java and run tests: ``` ./gradlew build ```...

Yes I agree with that problem on `libc++_shared.so`. We could link it statically into `libroc.so` and remove that dependency on `libroc_jni.so`; regarding synchronization we can use directly `pthread_mutex` in my...

For android library we can remove STL dependency with `-DANDROID_STL=none` arguments on android gradle plugin; regarding `libroc.so` can we set `LDFLAGS=-static-libstdc++` before compiling with scons or do you have a...

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

> 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...

> 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....

Since the gradle `cpp-library` plugin doesn't cross-compile, in my opinion it's better to write a custom gradle plugin based on cmake (taking inspiration for example from [gradle native cmake library](https://github.com/gradle/native-samples/tree/master/cpp/cmake-library)...