Slashdot Mirror
Microsoft Continues Porting Visual C++ To Linux (microsoft.com)
Long-time Slashdot reader Billly Gates shared some news from Microsoft's Visual C++ blog: Visual Studio 2017 now lets developers write C++ code for Linux desktops, servers, and other devices without an extension, targeting specific architectures, including ARM:
Visual Studio will automatically copy and remotely build your sources and can launch your application with the debugger... Today Visual Studio only supports building remotely on the Linux target machine. It is not limited to specific Linux distros, but we do have dependencies on the presence of some tools. Specifically, we need openssh-server, g++, gdb and gdbserver.
You do realise that "remote" in this instance is you own Linux machine, right? Not a closed build server owned by Microsoft - you are asked for connection information to a Linux machine so VS can copy sources, build, run and connect the debugger.
A 30 second scan of the link in the summary would have shown that up, but that might have held up your shit posting...
If I were going to switch to anything other than gcc (or support anything in addition to it), I would first go for clang and then maybe icc. I can't imagine what value vc++ would add over those.
gcc's warning/error messages are pretty awful and I really like that clangs almost always point me precisely to where the problem is, as opposed to where the problem finally made the compiler lose its mind. Does vcc++ improve on clang in that respect? If it does, I could supporting it as a build target for automated builds to get the nice diagnostics (I do this now for a project with clang), but I can't imagine it would be worthwhile for something that gets deployed.
icc is nice if you are on Intel hardware and want the sooper-dooper extra special optimizations, but that is about it.