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 here:
https://github.com/roc-streaming/roc-toolkit/blob/271ddf27eb3fae0273b5f8488a3114e70f1acfdb/src/public_api/include/roc/log.h#L58
Consider passing the following fields to jul:
- file and line (not strictly necessary, generally libroc logs are useful without this information too)
- time
- pid and tid (or maybe only tid)
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 here:
https://github.com/roc-streaming/roc-toolkit/blob/271ddf27eb3fae0273b5f8488a3114e70f1acfdb/src/public_api/include/roc/log.h#L58
Consider passing the following fields to jul: