← Back to index | Original Bugzilla link

Bug 17877 – Missing library path in LDC settings

Status: RESOLVED
Resolution: FIXED
Severity: normal
Priority: P1
Component: visuald
Product: D
Version: D2
Platform: x86_64
OS: Windows
Creation time: 2017-10-04T21:56:28Z
Last change time: 2017-12-02T16:42:27Z
Assigned to: No Owner
Creator: Thomas

Comments

Comment #0 by thomas.hedstrom — 2017-10-04T21:56:28Z

kernel32.lib is not found when compiling for LDC 32/64bit. The reason seems to be that paths in the "LDC Directories" are only: $(VCTOOLSINSTALLDIR)lib\x64 $(UCRTSdkDir)Lib\$(UCRTVersion)\ucrt\x64 but kernel32.lib is placed in: $(UCRTSdkDir)Lib\$(UCRTVersion)\um\x64 Adding this third path, makes LDC work in my system. Windows 10 VS2017 Community 15.3.5 VisualD v0.46.0-beta1

Comment #1 by greensunny12 — 2017-10-05T14:15:00Z

This is the issue tracker for DMD, Druntime and Phobos. Please report LDC issues at their own issue tracker: https://github.com/ldc-developers/ldc/issues Thanks!

Comment #2 by r.sagitario — 2017-10-05T17:40:56Z

It's a Visual D issue, so it's appropriate here. Detection of the Windows SDK is failing for the Win 10 SDK, the slightly more exact entry for it would be $(WindowsSDKDir)Lib\$(WindowsSDKVersion)\um\x64

Comment #3 by thomas.hedstrom — 2017-10-16T16:59:22Z

Sorry for the delay... Tested echoing the set vars during build with the following result: WindowsSDKDir= UCRTSdkDir=C:\Program Files (x86)\Windows Kits\10\ So, only UCRTSdkDir would work here. Might be SDK version that differs. Under VS Installer "Desktop development with C++" options I have the following selected: VC++ 2017 v141 toolset (x86,x64) C++ profiling tools Windows 10 SDK (10.0.15063.0) .... Visual C++ tools for CMake Visual C++ ATL support no more

Comment #4 by r.sagitario — 2017-12-02T16:42:27Z

Win 10 SDK detection fixed in https://github.com/dlang/visuald/releases/tag/v0.46.0