[Issue 15106] Optlink executed with LDC as compiler?

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=15106

--- Comment #5 from Sobirari Muhomori <dfj1esp02 at sneakemail.com> ---
(In reply to Manu from comment #4)
> I think those command prompts demonstrate that MS understand the pathing
> struggle, and they fixed it in a way that other stuff on the users systems
> tends not to interfere with.

The solution is to NOT put the toolchain in PATH system-wide. That's the best
solution so far and the way MS toolchain works (and the very reason why MS
toolchains can work side by side with each other on the same system).

> Perhaps LDC (or VisualD?) should leverage those command prompts when
> building against the MSVC ecosystem (ie, LDC, DMD), rather than just hoping
> the path is configured correctly? Windows users don't do path management,
> it's always a complete mess.

The mess is done by dmd installer to address demands that dmd must work out of
the box no matter what. This is done by mangling PATH system-wide to dmd's
bidding and breaking other tools, but it achieves the goal: dmd works. MS tools
don't mangle PATH because it's not interoperable - the very issue you suffer.
So whoever touches PATH is responsible for the mess - it's dmd installer in
this case.

--