[Issue 15106] Optlink executed with LDC as compiler?

[via Digitalmars-d-bugs]

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

--- Comment #4 from Manu <turkeyman at gmail.com> ---
But I've _never_ had a single problem with visual studio of this sort in 16
years. I often have 3 or 4 versions of VS installed in parallel, they all just
work together.
Those command prompts do exist, but they're transparent to the end-user, it
runs them when it needs them.

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.

My point is, the D ecosystem across the board (not just picking on LDC here),
needs to be more creative about solving this problem. It's tiring, and it
basically hasn't changed for 6 years that I've been here. I had 3 distinct
instances of pathing problem yesterday alone.

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.

--