Multiple definitions of Base64_Encode() when WolfSSL is used. about azure-c-shared-utility

[anhashia]

Hi @ArsalanSaleemGhuman

I had chance to look at this. Yeah, it can be an issue if you try to build WOLF SSL with WOLFSSL_BASE64_ENCODE define. But I was also able to build WOLF SSL on Windows without this define.

Is there any reason that you want to use WOLFSSL_BASE64_ENCODE with WOLF SSL and not use implementation in azure_c_shared_utility while using Azure IoT C SDK ? Trying to understand the use case here.

For your reference, currently C SDK does have TI RTOS CC3200 using WOLF SSL as a supported configuration.
https://github.com/Azure/azure-iot-sdk-c/blob/master/build_all/tirtos/Makefile#L36

[ArsalanSaleemGhuman]

This problem doesn't occur in the default build of Nucleus RTOS with Azure. But in a more advanced configuration, the problem may occur because some Nucleus RTOS components rely on the WolfSSL library, so the library would be included in the build in such cases. So it would be a nice-to-have item to fix this naming conflict, if easily possible.

[anhashia]

Fix checked in 11f504a