[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 Rainer Schuetze changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 --- Comment #9 from Rainer Schuetze --- I tweaked the defaults in https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1 and added browse buttons to set/add path entries. Visual D also tries to detect

[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 --- Comment #10 from Manu --- (In reply to Rainer Schuetze from comment #9) > but I suspect that these should just be different compilers. This is true. Where do you think VisualD stands in defining different toolchains like

[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 --- Comment #8 from Manu turkey...@gmail.com --- (In reply to Rainer Schuetze from comment #3) It's LDC that is calling lib.exe, so probably the best Visual D can do is to add the path to the VC bin folder to the Executable Paths by default. For

[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 --- Comment #4 from Manu turkey...@gmail.com --- Oh okay. Will adding it to the Executable Paths cause it to take precedence over other paths already in $PATH? MinGW LDC is probably of fairly limited use... I imagine more MinGW users would want to

[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 --- Comment #3 from Rainer Schuetze r.sagita...@gmx.de --- It's LDC that is calling lib.exe, so probably the best Visual D can do is to add the path to the VC bin folder to the Executable Paths by default. For the mingw version of LDC, it cannot

[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 --- Comment #7 from Rainer Schuetze r.sagita...@gmx.de --- I can't imagine a situation where I don't care about the runtime in my work :/ If you don't build a large application, but just a small command line tool that you don't want to distribute,

[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 --- Comment #5 from Rainer Schuetze r.sagita...@gmx.de --- Oh okay. Will adding it to the Executable Paths cause it to take precedence over other paths already in $PATH? Yes, it is prepended to PATH. MinGW LDC is probably of fairly limited

[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 --- Comment #6 from Manu turkey...@gmail.com --- I can't imagine a situation where I don't care about the runtime in my work :/ But sure, in the cases where you want to use MinGW, would you typically reach for GDC or LDC though? --

[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 Rainer Schuetze r.sagita...@gmx.de changed: What|Removed |Added CC||r.sagita...@gmx.de ---

[Issue 14558] Attempts to link with DMD when using MSVC LDC under VisualD

https://issues.dlang.org/show_bug.cgi?id=14558 --- Comment #2 from Manu turkey...@gmail.com --- That sounds like the problem. It is in the path. I don't think it's good to rely on user path configuration for this to work. There is already code where VisualD overrides the VS tool paths with the