Victor Gaydov
Victor Gaydov
Here are some things we need to document in README. **For user - what are requirements** * For desktop - range of supported JDK versions needed when building the project...
Currently, when CI builds AAR, it uses libroc from master branch of roc-toolkit. It's not good because this way AAR builds are not reproducible. What we need to do: -...
Currently, I'm able to build roc-java using OpenJDK 8, but not OpenJDK 17. OpenJDK 8 is not available in next debian stable candidate, so it would be nice to fix...
New libroc API (starting from 0.2), log messages provide more granular information. Instead of three arguments (level, component, message), logging callback in native library now receives a struct roc_log_message, defined...
packetInterleaving should be boolean, not integer. We need to update RocSenderConfig, RocSenderConfig.Builder, and their methods, as well as the JNI side.
There are a few android-related versions that we specify in build scripts and CI: * `Android NDK version`. Does not affect runtime requirements. Generally **should be set to latest available...
Currently, Android minSdkVersion (i.e. Android API level which we support) is set to `26`: https://github.com/roc-streaming/roc-java/blob/b3096658ed7c7f34e42272d51d6d39f5bb38646c/android/roc-android/build.gradle#L26 **We should check whether this value can be lowered or it is indeed minimum version...
We build two versions of AAR, debug and release, and both use release version of native libroc.so. It would be convenient to build debug version of libroc, and use it...
On Android, if AAR or APK has native libraries depending on libc++_shared.so (C++ STL from Clang), they should ship a copy of the library. This, theoretically, may lead to problems...
Automatically build and publish our library. Maybe use jitpack.io or Maven Central or JCenter.