ldc2 Windows

Carl Sturtivant sturtivant at gmail.com
Tue Oct 23 14:09:18 UTC 2018


On Tuesday, 16 October 2018 at 20:14:03 UTC, Carl Sturtivant 
wrote:
> Based upon all this I tried first setting VSINSTALLDIR and 
> adding to PATH the path to the linker. And setting LIB. 
> (Apparently LIBPATH is for the compiler, not the linker.) This 
> did the job! I'll put the path to the linker and the 
> directories in LIB into switches in etc/ldc2.conf and I'll have 
> a clean setup.

Specifically for persons new to D on windows who want to follow 
in these footsteps, the values needed proved to be as follows on 
64 bit Windows 10.

I obtained these by running the commands listed below in a `x64 
Native Tools Command Prompt for VS 2017` under `Visual Studio 
2017\Visual Studio Tools\VC` from the start menu. Probably you 
should do that.


VSINSTALLDIR
from `echo %VSINSTALLDIR%`
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\

LIB
from `echo %LIB%`
C:\Program Files (x86)\Microsoft Visual 
Studio\2017\BuildTools\VC\Tools\MSVC\14.15.26726\lib\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\ucrt\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\um\x64;

PATH --- addition to PATH needed to find link.exe
from `where link`
C:\Program Files (x86)\Microsoft Visual 
Studio\2017\BuildTools\VC\Tools\MSVC\14.15.26726\bin\Hostx64\x64\




More information about the digitalmars-d-ldc mailing list