mbedtls redefined warnings about anjay-esp32-client HOT 2 CLOSED

This stems from some API changes over the history of Mbed TLS:

• Before Mbed TLS 2.7, there were only functions such as mbedtls_md5_starts(), which returned void
• In Mbed TLS 2.7, these functions got deprecated, with new APIs called e.g. mbedtls_md5_starts_ret() added, able to return an error code as int
• In Mbed TLS 3.0, the old deprecated APIs got removed, and the *_ret() APIs have been renamed to the names identical to the old pre-2.7 function names

avs_commons uses the Mbed TLS 3.0 APIs, and includes these #defines to bridge the API differences between versions and stay compatible with Mbed TLS 2.x, including the pre-2.7 versions.

These macros seem to conflict with some macros in ESP-IDF, but we have checked the consequences of that and verified that this is harmless.

The warnings will almost certainly disappear once ESP-IDF is updated to use Mbed TLS 3.x. Due to that, the harmlessness of the warning and the fact that it comes from compatibility code that affects platforms other than ESP-IDF as well, we decided to just ignore the issue and let the warning be reported.

from anjay-esp32-client.

@kFYatek
Thanks for the quick response and clarify it's harmless.

from anjay-esp32-client.