Using Azure C embedded SDK in one of the samples

[Bhargav Kinnal]

I am evaluating the usage of Azure C embedded SDK (https://azure.github.io/azure-sdk-for-c/) in one of the nRF 9160DK development samples (https_client)

The Azure C SDK is added via fetchContent of Cmake. And I use the nRF connect to build the https_client sample. 

While the compilation works well. I see issues during the linking as follows

c:/users/ncs/v1.8.0/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: error: _deps/azuresdkforc-build/sdk/src/azure/iot/libaz_iot_provisioning.a(az_iot_provisioning_client_sas.c.obj): conflicting CPU architectures 17/2
c:/users/ncs/v1.8.0/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: failed to merge target specific data of file _deps/azuresdkforc-build/sdk/src/azure/iot/libaz_iot_provisioning.a(az_iot_provisioning_client_sas.c.obj)

Am I missing something? I am working on windows and using the nRF connect setup on my VS-code. 

[Hakon]

Hello,

instead of using a third party SDK for the nrf9160, I would recommend you just use the NCS sample https://github.com/nrfconnect/sdk-nrf/tree/main/samples/nrf9160/azure_iot_hub.

[Bhargav Kinnal]

Thanks for your answer. Using Azure SDK is not optional for me. Is there a way you could help me solve this build issue? Thank you. I will also look at using the NCS sample that you suggested. 

[Hakon]

Bhargav Kinnal said:

Is there a way you could help me solve this build issue?

We don't provide support for this sort of third party SDK. You should just use the NCS instead.

[Bhargav Kinnal]

The issue was a wrong compiler flag for the target architecture and soft FPU. Setting the right flags solved the issue.