Hmm, it is already happening, isn't it? There is already a support of MSVCR in git's code base. I am referring to replacing that current support of 'older' MSVCR in favor of the latest one, so to make the git's code base comparatively coherent and organized (as some/many instances of #ifdef _MSC_VER and #if define (_MSC_VER) && _MSC_VER < xxx etc. will be gone, for instance we don't need fallback for sprint or snprintf since C99 std support for those is provisioned). > ---------------------------------------- >> From: jacob.keller@xxxxxxxxx >> Date: Sun, 26 Jul 2015 00:15:10 -0700 >> Subject: Re: FeatureRequest: Build improvements for Windows >> To: danglingpointer@xxxxxxxxxxx >> CC: git@xxxxxxxxxxxxxxx >> >> On Sat, Jul 25, 2015 at 11:23 PM, Dangling Pointer >> <danglingpointer@xxxxxxxxxxx> wrote: >>> Hello, >>> >>> In my understanding, the ratio between the mere consumers of git on Windows vs. people who compile git for Windows is 100,000 : 1. If there is a breaking change in the workflow of the latter set, who use Visual Studio to build git from source, I assume that is doable given a good reason, hence this post. >>> >>> With VS 2015, C99 support is "finally" added with some C11 features as well. See this blog: http://blogs.msdn.com/b/vcblog/archive/2015/06/19/c-11-14-17-features-in-vs-2015-rtm.aspx. One of the edition of new VS is Community edition, which is like professional edition but is free (also much superior than Express edition) and meant for open source projects. VS2015 also has the ability to target compiler for Wind-XP. >>> >> >> I think the big issue is whether it has support for the various unix >> interfaces and unix shell commands we use. MinGW/MSYS comes with >> support for the unix interface, which I don't believe is that actually >> supported via MSYS and I don't know if VS2015 is supported? I don't >> think it's due to the C99 but due to need of posix interface which is >> not normally (fully) provided by Windows. >> >> Regards, >> Jake -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html