After a week spent on this I could manage to solve the problem. Actually, the problem was with Visual Studio 2019 installation. For some strange reason, the command VsDevCmd messes with all the needed environmental variables to do a proper compilation. It is something related with having more than one version of Windows SDK in the computer. It shouldn't be a problem as SM "asked" VS2019 the proper setup to compile its files. The toolkit with all needed headers and libraries is the 10.0.19041.0 version. You can find the toolkits in (if you haven't changed the standard path):

C:\Program Files (x86)\Windows Kits\10\Include

There is a folder for each version:

Solution:

1. Select custom setup for the compiler;
2. Add -winsdk=10.0.19041.0 command to the line "Visual C++ setup script arguments";
3. Click Verify Compiler, it is expected to succeed;
4. Click OK.

My compiler options screen after setup:

Hope this helps anyone with the same problem!

Relevant link: https://renenyffenegger.ch/notes/Windows/dirs/Program-Files-x86/Microsoft-Visual-Studio/version/edition/Common7/Tools/VsDevCmd_bat

The HAVE_INTTYPES_H macro is set because Visual Studio should have the inttypes.h header since VS2013.

Just to make sure did you verify that the selected compiler was changed to you newly installed VS 2017?

I've installed the full "Visual C++ build tools" workload for Vs 2017

That is not communicated that clearly, but you are not supposed to change anything during the installation, the necessary components should be preselected.

For me the component that seems to add the inttypes.h file is Windows Universal CRT SDK

You are most likely missing a necessary component of Visual Build Tools. I would suggest that you install the compiler by pressing the "Check for Compatible Compiler" button in the dialog shown above. This will preselect the necessary components of Visual Studio Build Tools that you need to install.

Otto