Mbed TLS is now part of TrustedFirmware.org.

Making mbedTLS /W4 compliant for Visual Studio compiler

Mar 23, 2017 00:38
Pawel Winogrodzki

Hi all,

We're using mbedTLS in the IoTivity project. As part of our work we're making sure that there are no level 4 warnings during compilation (Visual Studio 2013 and 2015 for x86 and amd64 architectures). I have already made the required changes for mbedTLS but they are only local to IoTivity and now I was wondering if you'd be interested in having them integrated in the "development" branch?

I'd be happy to create a pull request with all the changes. Please let me know, what do you think about this idea.

Thanks, Pawel

Mar 23, 2017 10:37
Ron Eldor

Hi Pawel,
Thanks for your offering!
As an open source project, we are always grateful to receive contributions from the community, as long as they follow the guidelines listed in the following link
mbed TLS Team member

Mar 24, 2017 02:10
Pawel Winogrodzki

Thanks, Ron. I've created a pull request.

I could use some help regarding the messages I get from check-generated-files.sh and check-names.sh. Where can I find some information about them?

Apr 3, 2017 10:19
Ron Eldor

Hi Pawel,
It is recommended that Pull Request specific questions should be addressed in the Pull Request itself, so it could remain in context.
I see in the Pull Request that only check-names.sh has failed. Am I missing something?
In case of failures in the CI, I suggest you run the scripts in your local folder (they are located in tests/scripts folder) to help you understand the reason for failures. As you can see in the check-names script:


and in the CI log you see the following:

$ tests/scripts/check-names.sh
Analysing source code...
1193 macros
     146 enum-consts
977 identifiers

From the output it means that tests/scripts/list-symbols.sh has failed.
The returned error was 2 (ENOENT), I am guessing that it is because libmbed*.a was not found in the nm command, because of compilation error (fatal error: 'winsock2.h' file not found), which returned error 2
I hope this helps
mbed TLS Team member