-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
amazon-kvs-producer-sdk fails to create streams due to dependency commitish mismatches #1701
Comments
Hi, |
fix: aws4embeddedlinux#1701 add ptest for amazon-kvs-producer-pic changes acc. to oelint-adv
fix: #1701 add ptest for amazon-kvs-producer-pic changes acc. to oelint-adv
could you please check if my commit fix your problem. |
So, the commit looks good. But I cannot build it to test. I tried building meta-aws/master-next with kirkstone and it failed to build with a linking error: generated error calling This is my amazon-kvs-producer-sdk-cpp_%.bbappend
` |
fix: aws4embeddedlinux#1701 add ptest for amazon-kvs-producer-pic changes acc. to oelint-adv
my recent commit now disable building the test and add an option the configure gstreamer via packageconfig. This should make your bbappend obsolete. Please try to confirm. |
fix: aws4embeddedlinux#1701 add ptest for amazon-kvs-producer-pic changes acc. to oelint-adv
fix: aws4embeddedlinux#1701 add ptest for amazon-kvs-producer-pic changes acc. to oelint-adv (cherry picked from commit 3d11cbe)
fix: aws4embeddedlinux#1701 add ptest for amazon-kvs-producer-pic changes acc. to oelint-adv (cherry picked from commit 3d11cbe)
fix: aws4embeddedlinux#1701 add ptest for amazon-kvs-producer-pic changes acc. to oelint-adv (cherry picked from commit 3d11cbe)
fix: aws4embeddedlinux#1701 add ptest for amazon-kvs-producer-pic changes acc. to oelint-adv (cherry picked from commit 3d11cbe)
fix: #1701 add ptest for amazon-kvs-producer-pic changes acc. to oelint-adv
Using kirkstone, I built and installed using t08d62031c3db8 on master-next.
ant the resulting binary ran, created streams on the fly, and the video was viewable. ty!!! |
cool, this change will be merged into kirkstone till tmr. |
Hi there, I'd like to reopen the issue, since I am getting the |
Hi, |
Hi, thanks for your reply. Bumping yocto and supporting the latest releases is planned, unfortunately the versions to support on our side is determined by the various BSP layers that we depend on, some of them still provide support only for up to mickledore at the moment. Can you point to me the back port fix you are referring to? If it is cherry-pickable, I can test it and suggest to apply it on the meta-aws mickledore branch, otherwise I'll bbappend the fix onto 3.4.1 on my side. |
Hi, meant just copying the whole folder: https://github.com/aws4embeddedlinux/meta-aws/tree/scarthgap/recipes-sdk/amazon-kvs-producer-sdk to mickledore and see if that works. |
@thomas-roos what I've done is used the scarthgap branch for meta-aws and force |
Give me 30min - I'm about to backport this. |
I do not have any compile issues - this is the backport PR: #9154 |
Merged, and also merged to mickledore branch. Just do an update. Please provide feedback. |
I've used your 2024-07-25_mickledore-next_backport-kvs branch and also latest mickledore and this results in the same It is interesting that you do not have an error though. Do you have a successful build after running |
I see now the issue. This is understood. Will dive into this. |
This is a Cmake link error as it seems: awslabs/amazon-kinesis-video-streams-producer-sdk-cpp#1197 Patched it here: #9168 please confirm |
libgstkvssink.so is now being built, tested on both mickledore-next and scarthgap-next, feel free to add my Tested-by! |
I am building amazon-kvs-producer-sdk-cpp_3.3.1.bb for Yocto kirkstone. I previously used 3.3.0 with dunfell. That worked fine in that I could create and push video streams from my device. With 3.3.1 I found that we were no longer able to create streams. We could only publish to streams that had already been created. We are building with gstreamer=ON.
There's a lot of numbers(commits) coming up, so I'll try to be clear.
the meta-aws I am using is 09db183 which is the kirkstone branch.
On that branch, the 3 recipes I need are using the following commits:
amazon-kvs-producer-pic_git.bb
SRCREV = "dc4bc6cb87cf97cd3b1dc3e8027e0c75cdfa13b3"
amazon-kvs-producer-sdk-c_1.4.1.bb
SRCREV = "80c74ac9200b58427a8fcb7782a03b1774020983"
amazon-kvs-producer-sdk-cpp_3.3.1.bb
SRCREV = "70f74f14cf27b09f71dc1889f36eb6e04cdd90a8"
.
Building/installing the above results in the gstreamer kvsssink not being able to create streams.
If we checkout
amazon-kvs-producer-sdk-cpp_3.3.1.bb
SRCREV = "70f74f14cf27b09f71dc1889f36eb6e04cdd90a8"
and look inside the CMake/Dependencies/libkvscproducer-CMakeLists.txt it calls for commit 79da5b6d6ad67560cc08530f967e9187a6d1c594 for the amazon-kvs-producer-sdk-c repo.
If we pull the amazon-kvs-producer-sdk-c repo and checkout the 79da5b commit and look inside the CMake/Dependencies/libkvspic-CMakeLists.txt we see that it calls for commit c8325887faa3a4a296c4367b281c778be69875b6 from the amazon-kvs-producer-pic repo.
If I use a bbappend to override the SRCREV for both the producer-sdk-c and the producer-pic to be consistent with the dependency chain in the CMake files, I can create and push video streams.
I am assuming that we should still be able to create streams from the device on kirkstone and that this is just a version mismatch and not a desired change in behavior?
I'm happy to submit the SRCREV overrides as a PR if that is desired/correct.
The text was updated successfully, but these errors were encountered: