Running DMD tests on Windows / build requirements

[kinke via Digitalmars-d]

On Sunday, 21 February 2016 at 16:45:14 UTC, Martin Krejcirik 
wrote:
> LINK : fatal error LNK1104: cannot open file 'libucrt.lib'
> --- errorlevel 1104
>
> Stock dmd doesn't require libucrt.lib. If I copy it to 
> dmd2\windows\lib64 a get:
>
> D:\devel\bugs>dmd -m64 utfbug
> DMD v2.068 DEBUG
> phobos64.lib(dmain2_629_47b.obj) : error LNK2019: unresolved 
> external
> symbol __iob_func referenced in function _d_run_main
> phobos64.lib(dmain2_629_47b.obj) : error LNK2019: unresolved 
> external
> symbol _set_output_format referenced in function _d_run_main
> phobos64.lib(config_487_452.obj) : error LNK2019: unresolved 
> external
> symbol sscanf referenced in function
> _D2gc6config13__T5parseHTfZ5parseFNbNiAxaKAxaKfZb
> utfbug.exe : fatal error LNK1120: 3 unresolved externals
> --- errorlevel 1120

I wouldn't copy headers and libs around, just use properly set-up 
environment variables (INCLUDE, LIB, LIBPATH etc. - these are set 
by Visual Studio's vcvarsall.bat, maybe there's something similar 
for the build tools package as well).
Anyway, the latest linking errors are due to some heavy changes 
in Microsoft's C runtime with VS 2015. Phobos v2.068 doesn't 
support it yet, so you may want to try the latest version instead.