On 22.05.2017 03:54, Enjoys Math wrote:
[...]
C:\Users\Gabe\AppData\Roaming\dub\packages\pyd-0.9.9\pyd\\infrastructure\windows\python27_digitalmars.lib+
user32.lib+
kernel32.lib/NOMAP/CO/NOI/DELEXE
LINK : fatal error LNK1181: cannot open input file 'obj\debug\dummy\dummy\dummy\dummy\dummy\dummy\dummy\pegparser\..\source\led_ux_grammar.obj+' Building C:\Users\Gabe\Dropbox\MyProjects\___SOUND_UNITED\LED_UX_Designer\lang\PEGparser\PEGparser.exe failed! Details saved as "file://C:\Users\Gabe\Dropbox\MyProjects\___SOUND_UNITED\LED_UX_Designer\lang\PEGparser\.dub\obj\debug\dummy\dummy\dummy\dummy\dummy\dummy\dummy\pegparser\pegparser.buildlog.html"
========== Build: 0 succeeded, 1 failed, 1 up-to-date, 0 skipped ==========

This looks like the wrong link.exe has been found in path. When building for Win32/x86 the default is to use optlink that is installed with dmd. The error message is issued by MS link instead.

I suspect the DMD installation folder is not set correctly (check Tools->Options->Projects and Solutions->Visual D Settings->DMD directories). Please also check the executable search paths below, they should include "$(DMDInstallDir)windows\bin". There was a bug in Visual D 0.44.0 where a bad character sneaked into the path to DMD's bin folder.

> Opening any of the dub.json files with red X's opens them, but then immediately crashes VS.

The red cross means it's not part of the build, so that's correct.

The crash is not ok. I can reproduce it, seems to happen due to a function not being implemented (which seems fine for other files).

Reply via email to