[Issue 19624] x64 Build paths for VS 2017 are wrong after installation. VCINSTALL is deeper
d-bugmail at puremagic.com
d-bugmail at puremagic.com
Mon Jan 28 22:18:41 UTC 2019
https://issues.dlang.org/show_bug.cgi?id=19624
Rainer Schuetze <r.sagitario at gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |r.sagitario at gmx.de
--- Comment #1 from Rainer Schuetze <r.sagitario at gmx.de> ---
I suspect your installation without any workload caused the default paths to be
wrong. Here are the usual settings for DMD/x64:
Executable paths:
$(VCTOOLSINSTALLDIR)bin\HostX86\x86
$(VSINSTALLDIR)Common7\IDE
$(WindowsSdkDir)bin
$(DMDInstallDir)windows\bin
Library paths:
$(VCTOOLSINSTALLDIR)lib\x64
$(UCRTSdkDir)Lib\$(UCRTVersion)\ucrt\x64
$(WindowsSdkDir)lib\$(WindowsSdkVersion)\um\x64
Linker:
$(VCTOOLSINSTALLDIR)bin\HostX86\x86\link.exe
>While it turned out to be important AND undocumented that VS needs
>"Visual Studio extension development" extension I have the feeling
> that MSVC folder content was created only after "Desktop development
> with C++ " installation in VS => right? Should be in docu as well.
The missing assembly probably comes with any other "workload" aswell as it is
used by most project wizars. It's true that "C++ development" is expected so
far, I wasn't aware that you could almost get something working without that.
--
More information about the Digitalmars-d-bugs
mailing list