From: Dangling Pointer <danglingpointer@outlook.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: FW: FeatureRequest: Build improvements for Windows
Date: Sun, 26 Jul 2015 08:45:42 +0000 [thread overview]
Message-ID: <BAY169-W75E45600196FA9E4B9A20CA78F0@phx.gbl> (raw)
In-Reply-To: <BAY169-W84A0734CACD22511DE9B5BA78F0@phx.gbl>
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@gmail.com
>> Date: Sun, 26 Jul 2015 00:15:10 -0700
>> Subject: Re: FeatureRequest: Build improvements for Windows
>> To: danglingpointer@outlook.com
>> CC: git@vger.kernel.org
>>
>> On Sat, Jul 25, 2015 at 11:23 PM, Dangling Pointer
>> <danglingpointer@outlook.com> 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
next prev parent reply other threads:[~2015-07-26 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY169-W8210AC5C69796A61AD2236A78F0@phx.gbl>
2015-07-26 6:23 ` FeatureRequest: Build improvements for Windows Dangling Pointer
2015-07-26 7:15 ` Jacob Keller
[not found] ` <BAY169-W84A0734CACD22511DE9B5BA78F0@phx.gbl>
2015-07-26 8:45 ` Dangling Pointer [this message]
2015-07-26 11:27 ` Philip Oakley
2015-07-26 15:47 ` Dangling Pointer
2015-07-26 16:52 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAY169-W75E45600196FA9E4B9A20CA78F0@phx.gbl \
--to=danglingpointer@outlook.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).