You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My understanding is that Axis will no longer support containerized device applications in the future. So, I'm looking for an alternative to create streams to Kinesis in Native ACAP SDK apps.
Is it possible to extract the *.so file from the Docker container of this project and place it directly in the camera system?
If you could provide guidance on how to achieve this, it would be awesome.
The text was updated successfully, but these errors were encountered:
Indeed a real example would really be appreciated.
For a POC, I was able to cross compile the producer cpp and the gstreamer plugin (kvssink).
I encountered various problems, notably with the openssl version required for the producer. So I cross compiled the dependencies myself. Here are some usefull info to get started
I also had a lot of linking problem running my app/kvssink so i used the following branch to get a .so statically linked to the amazon sdk and modified the install rpath for my other dependencies.
On the CPP side, my app just launches a gstreamer pipeline equivalent to this repo.
One of the bad point is that the version of gstreamer and common plugins used are those already present on the axis os.
I'm not allowed to share my code/build process.
At this time it's only a POC and it's clearly not ready for more serious use.
Hope this help, waiting for a better way / example on this topic
Hello, thanks for the project.
My understanding is that Axis will no longer support containerized device applications in the future. So, I'm looking for an alternative to create streams to Kinesis in Native ACAP SDK apps.
Is it possible to extract the *.so file from the Docker container of this project and place it directly in the camera system?
If you could provide guidance on how to achieve this, it would be awesome.
The text was updated successfully, but these errors were encountered: