3 ms·
> Today we only support building remotely on the Linux target machine. That's not quite what I suspected this meant. Buuuut, still -- good for you, Microsoft.
by wyldfire 11y ago
> Today we only support building remotely on the Linux target machine.
That's not quite what I suspected this meant.
Buuuut, still -- good for you, Microsoft. These are the kinds of changes you need in order to attract developers.
- robotdad 11y agoI've been puzzling over this all night. I think I finally got your meaning. I have an IoT focus so "target" doesn't have a negative connotation to me. :)
- wyldfire 11y agoWell, it's not necessarily negative, but the scope of the feature delivered is much smaller if what the team says they've done is integrated ssh/scp/gdb into VC++. When I read the headline after having read the bit about native linux binaries, I thought "wowsers MS went full linux support!" Still, it's an excellent achievement and it seems clear that they wanted to announce this at the same time. They right-sized the scope of the VC++ work to match what could be accomplished in the time allowed. I would be thrilled if Microsoft's next move would be to transition to an LLVM/clang based engine underneath VC++. IMO their distinguishing feature for VC++ is not the compiler engine. This would be the kind of lean maneuver that they're trying to steer towards these days.
- robotdad 11y agoSorry, never meant to mislead that VS was on Linux. Is this the sort of thing you are looking for with respect to clang? https://blogs.msdn.microsoft.com/vcblog/2016/01/20/clang-with-microsoft-codegen-january-2016-released/ https://blogs.msdn.microsoft.com/vcblog/2016/01/20/clang-wit... We don't have clang support for Linux yet, something we are looking at. Lots to do. :)