Closed aka-demik closed 7 years ago
workspace-d hung up, did you compile it with LDC or DMD?
code-d automatically build workspace-d after update.
Both dmd and ldc2 is available. Somehow I can check which compiler was used?
> dmd --version
DMD32 D Compiler v2.072.2
> ldc2 --version v
LDC - the LLVM D compiler (1.1.0-beta6):
based on DMD v2.071.2 and LLVM 3.9.0
built with LDC - the LLVM D compiler (1.1.0-beta6)
Default target: x86_64-pc-windows-msvc
Host CPU: sandybridge
http://dlang.org - http://wiki.dlang.org/LDC
Registered Targets:
arm - ARM
armeb - ARM (big endian)
mips - Mips
mips64 - Mips64 [experimental]
mips64el - Mips64el [experimental]
mipsel - Mipsel
ppc32 - PowerPC 32
ppc64 - PowerPC 64
ppc64le - PowerPC 64 LE
sparc - Sparc
sparcel - Sparc LE
sparcv9 - Sparc V9
thumb - Thumb
thumbeb - Thumb (big endian)
x86 - 32-bit X86: Pentium-Pro and above
x86-64 - 64-bit X86: EM64T and AMD64
I rebuilt workspace-d using https://github.com/Pure-D/workspace-d/blob/master/install.bat
According to log, it used ldc2. And it works.
So does auto completion still hang now?
Oh yeah, I forgot about #38
No. Now everything is working fine.
Maybe, dmd should not be used for automatic build workspace-d?
uh it should do that already, I'm gonna check on code-d later. Though it should have downloaded the prebuilt release for windows which is compiled using LDC. I think I will add a "Compiled with" to the version thing
Added compiler info in workspace-d master
It work fine from dcd-client:
But "Go to definition" (F12) and "Go to the symbol in the file" (Ctrl+Shift+O) does not work. vscode.log.zip