Linking issues VisualD generated vs Dub generated projects

Rainer Schuetze r.sagitario at gmx.de
Wed May 22 17:32:33 UTC 2019



On 22/05/2019 10:42, ShadoLight wrote:
> My *current* set of Library search paths (Tools -> Options -> VisualD
> Settings -> DMD -> x64) shows:
> $(VCINSTALLDIR)lib\amd64
> $(UniversalCRTSdkDir)Lib\$(UCRTVersion)\ucrt\x64
> $(UniversalCRTSdkDir)Lib\$(UCRTVersion)\ucrt\arm64
> $(DMDInstallDir)windows\bin

This looks pretty broken, you should not try to link ARM libraries.

The VS2015 default for x64 is:

$(VCINSTALLDIR)lib\amd64
$(UCRTSdkDir)Lib\$(UCRTVersion)\ucrt\x64

and for Win32-COFF:

$(VCINSTALLDIR)lib
$(UCRTSdkDir)Lib\$(UCRTVersion)\ucrt\x86

Starting with VS2015, the VC runtime requires the universal runtime (UCRT).

You can see the resulting paths in the build logs in the output
directory. The are passed to the linker with the /LIBPATH option.


More information about the Digitalmars-d-ide mailing list