KerstinKeller
KerstinKeller
So we have never before worked with CRIU. eCAL programs have a lot of resources (e.g. shared memory files, mutexes) which are shared between a publisher and a subscriber. Both...
And another note: Please don't start eCAL applications with sudo permissions, or if you do, please be aware that tasks started with sudo cannot communicate with started without sudo on...
@DownerCase thanks for this great hint! Setuptools-protobuf seems really promising. We have to see if it plays together with py-build-cmake, but worst case, we'll make two different packages, one with...
The good thing is that during build, we already have protobuf available. That's challenging with `setuptools-protobuf` as the user has to provide a protoc (which needs to be compatible with...
The c# files are already generated as part of the build. Which proto version did you upgrade to? I previously tested with 3.21.x (think x=12)..
Now that I think about it, it is more likely that something with restoring the nuget protobuf references is going wrong now. In the PR that introduced the protobuf related...
@AliothZhou have you tried out eCAL 5.13 and see if that fixes the issue? Can we close this issue?
Thanks for reporting. We are currently working on our Python bindings, and we will take a look at this issue.
Will be reimplemented.
We should be able to remove the restriction again.