search

intel-iot-devkit / meta-iot-cloud

OpenEmbedded layer to add support for multiple cloud IoT services including Microsoft Azure & Google Cloud Platform.
MIT License
70 stars 81 forks source link

Update aws-iot-device-sdk-cpp-v2 #157

Closed Rafq77 closed 1 year ago

Rafq77 commented 2 years ago

Is it possible to update the sdk to newer version? Currently is 1.12.6 at least 1.14.x would be preferred, because of the easier MqttClient handling and static ClientBootstrap instance.

I wanted to do it myself but I don't understand the full scope of the Build-static-and-shared-libs.patch.

srware commented 2 years ago

Hi @Rafq77 ,

Apologies I have been super busy recently so not had time to update any of the recipes. I will try and look into this in the next week or so.

The patches for static and shared libs are to try and make the AWS libraries conform with standard Linux packaging. Ideally when building a recipe Yocto likes to have both static and shared versions of a library where possible which it packages separately. It means applications which compile against these libraries can choose whether to statically link or ship the shared libs. By default (it might have changed) these AWS repos only allow you to build one or the other (default is static) and often the shared libraries have issues.

Rafq77 commented 2 years ago

Thank you for answering anyway :). I have downgraded my software to match the 1.12.x however it doesn't represent the quality that I'd prefer it would do. I consider my current solution as temporary until the meta layer would be updated. :)

Otherwise, if I understood you correctly, I could try making my own recipe of the sdk with strictly static lib support. However it would be error prone if I would adjust that patch to the newer sdk (>=1.14) version.

If any update to the layer would come, would it be within this year or not earlier than 2023?

srware commented 2 years ago

@Rafq77 , I should get some time this week to take a look at getting this updated.

There is also the AWS official layer which is likely more up to date and might be worth a go.

Rafq77 commented 2 years ago

I also thought about that but then I was thinking that you did adjust sdk-cpp-v2 in your layer here. Therefore I have asked here first :)

srware commented 2 years ago

@Rafq77 , I have tested the https://github.com/aws4embeddedlinux/meta-aws layer for all packages included in this layer and most of the issues I encountered previously have been fixed. I think it will be logical to deprecate the AWS recipes from this layer to prevent duplication and also make sure issues go back to AWS developers who have been assigned to support them.

Can you also test from your side and raise any issues you encounter using the official AWS repo?

Rafq77 commented 2 years ago

@srware Great to know, if there are now further dependencies I will try to change to meta-aws directly. This might take some time though (few weeks). I'll aim for a report before Christmas.

Rafq77 commented 1 year ago

Hey @srware , It required a bigger rework on our side, but going staright for the kikstone branch in meta-aws solved the problem for us and helped align all the dependencies to one common revision. Thank You, Merry Christmas and Happy New Year :)