It’s difficult to build VCV stuff with microsoft compilers. Far easier to do it exactly like the instructions say, which ends up running gcc in an msys2 shell.
But you are right - whatever was the compiler way back a few years ago - possibly stuff has changed enough that current compilers won’t work for VCV 0.5? Don’t know.
it’s a lot of work to maintain multi-compiler builds, especially when you’re also building deps, and your upstream dependencies may not have made a lot of effort for Windows. It would make things more difficult for Rack and plugin devs alike for an uncertain marginal improvement for only Windows builds.
Far simpler to maintain as generic and portable a toolchain as you can.
That said, I’d love it if it were easy to build and debug using VS. The debugger is superior.
I build all my algorithm code for both gcc and visual studio. The executable under visual studio is just a plain old command line program that runs a thousand or so unit tests. I do all the debugging in there.
I’m using MSYS2 and MinGW 64-bit, as suggested in the lineguide (in the past, and now).
I can setup and older version of the suite.
Do you know which version would be used in that era? More or less, don’t think some minor update will impact most of the building system…