[Issue 17808] VisualD doesn't work if Visual Studio is installed to non-ASCII path

[via Digitalmars-d-bugs]

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

--- Comment #2 from karol.m.stasiak at gmail.com ---
(In reply to Rainer Schuetze from comment #1)

Please disregard whatever I wrote about the x86, it appears to had worked
correctly.

> Is it only visuald.pkgdef that is in the wrong place or are
> extension.vsixmanifest and vdlogo.ico affected aswell?

All three files were misplaced. In fact, there was not even a "Rainer Schuetze"
folder in the correct location.

> > as for the x64 target, the build script (x64\Debug\ConsoleApp1.build.cmd) contains wrong paths (two different ones!) as well, so VS cannot build anything. I've attached the file.
> 
> As a workaround you could try replacing $(VCInstallDir) and similar macros
> in the global options with the explicit path.

After I replaced the paths, the names in the build script were still wrong. It
appears that they are being encoded in CP582 and then decoded as Windows 1250,
so I used ˇ instead of ó and it managed to start the linker. Then it turned out
that the library paths are being decoded not as Windows 1250, but as UTF-8, and
VS didn't let me use ├│ in configuration values. I copied the libraries to
another location and finally I managed to get a working x64 executable and even
the debugger works, but I ended up having extra 500MB of static libraries.

So it kinda works, but it's hacky.

--