DMD Linker Issue on Windows

[tide]

On Thursday, 18 October 2018 at 16:21:00 UTC, Kai wrote:
> On Thursday, 18 October 2018 at 07:51:07 UTC, Andre Pany wrote:
>> On Thursday, 18 October 2018 at 00:24:29 UTC, Kai wrote:
>>> On Wednesday, 17 October 2018 at 17:44:34 UTC, Adam D. Ruppe 
>>> wrote:
>>>> [...]
>>>
>>>
>>> Hmm - wish it was so. When architecture not specified, the 
>>> linker crashes. When it's given, this happens (seems to be a 
>>> vibe issue?):
>>>
>>> [...]
>>
>> As far as I can see, there are some Windows libraries missing. 
>> These libraries are part of the Windows sdk  (You can use the 
>> vs build tools installer).
>>
>> Maybe we can include at least the libraries needed for vibe.d 
>> into the dmd Windows package?
>>
>> Kind regards
>> Andre
>
> I have multiple incarnations of both libs on my machine. I 
> copied the latest version of each into my the lib folder of the 
> DMD install path and it still fails with neither of them being 
> found.
>
> What am I doing wrong? Where do they need to go?
>
>
> Thanks for any help once more...

Who knows what path it is using for libs, I don't know if it does 
for lld-link and the config file was removed almost entirely. It 
determines these things on it's own and I'm not sure if there is 
any way to display what it is actually using without looking 
through the source. Try using the "-v" argument with DMD and look 
for the command it uses to run the linker. There might be a 
parameter passed for library paths there. Those two files were 
removed since VS 2015 I think, so odds are that's why it can't 
find it. If it is using a newer VS install path.