I was expecting that DUB / DMD & NMAKE take $LIB into account. I try to compile some stuff on x64.

This is LIB:

D:\develop\d-language\webchat> $Env:lib
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\LIB\amd64;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\LIB\amd64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.10240.0\ucrt\x64;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\lib\um\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.10240.0\um\x64;


This is the DUB call:

Linking...
dmd -of.dub\build\application-debug-windows-x86_64-dmd_2069-B25B434937830646D3F1C40AF40BEB8D\webchat.exe .dub\build\application-debug-windows-x86_64-dmd_2069-B25B434937830646D3F1C40AF40BEB8D\webchat.obj ..\vibe-d-0.7.26\lib\win-amd64\libeay32.lib ..\vibe-d-0.7.26\lib\win-amd64\ssleay32.lib ..\cairoD\cairoD.lib C:\Users\robby\AppData\Roaming\dub\packages\derelict-ft-1.0.2\lib\DerelictFT.lib C:\Users\robby\AppData\Roaming\dub\packages\derelict-util-2.0.4\lib\DerelictUtil.lib C:\Users\robby\AppData\Roaming\dub\packages\x11-1.0.9\x11.lib ..\vibe-d-0.7.26\vibe-d.lib wsock32.lib ws2_32.lib advapi32.lib user32.lib -LD:\develop\Cairo-VS\projects\x64\Debug\cairo.lib -LD:\develop\Cairo-VS\projects\x64\Debug\pixman.lib -m64 -m64 -m64 -m64 -m64 -m64 -g
LINK : fatal error LNK1104: cannot open file 'wsock32.lib'

Why isn't the "wsock32.lib" found? I really don't have a clue. I think that DMD's link step uses the MS tool. Is that right?

I really don't understand why the fundamental wsock32.lib is not found...

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster

On 2016-01-14 17:40:44 +0000, Robert M. Münch said:

> I was expecting that DUB / DMD & NMAKE take $LIB into account. I try to compile some stuff on x64.
> 
> This is LIB:
> 
> D:\develop\d-language\webchat> $Env:lib
> C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\LIB\amd64;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\LIB\amd64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.10240.0\ucrt\x64;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\lib\um\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.10240.0\um\x64;
> 
> 
> This is the DUB call:
> 
> Linking...
> dmd -of.dub\build\application-debug-windows-x86_64-dmd_2069-B25B434937830646D3F1C40AF40BEB8D\webchat.exe .dub\build\application-debug-windows-x86_64-dmd_2069-B25B434937830646D3F1C40AF40BEB8D\webchat.obj ..\vibe-d-0.7.26\lib\win-amd64\libeay32.lib ..\vibe-d-0.7.26\lib\win-amd64\ssleay32.lib ..\cairoD\cairoD.lib C:\Users\robby\AppData\Roaming\dub\packages\derelict-ft-1.0.2\lib\DerelictFT.lib C:\Users\robby\AppData\Roaming\dub\packages\derelict-util-2.0.4\lib\DerelictUtil.lib C:\Users\robby\AppData\Roaming\dub\packages\x11-1.0.9\x11.lib ..\vibe-d-0.7.26\vibe-d.lib wsock32.lib ws2_32.lib advapi32.lib user32.lib -LD:\develop\Cairo-VS\projects\x64\Debug\cairo.lib -LD:\develop\Cairo-VS\projects\x64\Debug\pixman.lib -m64 -m64 -m64 -m64 -m64 -m64 -g
> LINK : fatal error LNK1104: cannot open file 'wsock32.lib'
> 
> Why isn't the "wsock32.lib" found? I really don't have a clue. I think that DMD's link step uses the MS tool. Is that right?
> 
> I really don't understand why the fundamental wsock32.lib is not found...

Seems that some paths in sc.ini were not setup correctly. For x64 a Win10-SDK directory which doesn't exists was referenced.

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster

On Thursday, 14 January 2016 at 22:13:37 UTC, Robert M. Münch wrote:

>
> Seems that some paths in sc.ini were not setup correctly. For x64 a Win10-SDK directory which doesn't exists was referenced.

Did you install DMD manually? In that case, you will usually need to edit sc.ini to point to the proper VC and Win SDK directories. The DMD installer should detect your installation and configure it for you.

On 2016-01-15 00:36:57 +0000, Mike Parker said:

> Did you install DMD manually? In that case, you will usually need to edit sc.ini to point to the proper VC and Win SDK directories. The DMD installer should detect your installation and configure it for you.

I use Digger, hence this might be the cause. And, if one changes the VS installation after installing DMD, the manual changes are necessary as well. It's just that you need to remember it.

-- 
Robert M. Münch
http://www.saphirion.com
smarter | better | faster

I also ran into this issue because I upgraded VS and removed the old version. A quick re-install with the dmd .exe fixed it.