git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Junio C Hamano <gitster@pobox.com>,
	GIT Mailing-list <git@vger.kernel.org>,
	Jonathan Nieder <jrnieder@gmail.com>,
	mlevedahl@gmail.com
Subject: Re: [PATCH v2 2/2] cygwin: Remove the CYGWIN_V15_WIN32API build variable
Date: Fri, 3 May 2013 04:17:28 -0400	[thread overview]
Message-ID: <CAPig+cR3s4nzSOrG+=-MYEA4heTeMHpHQmAChWLEuFY2v+PhPA@mail.gmail.com> (raw)
In-Reply-To: <5182BE80.7060400@ramsay1.demon.co.uk>

On Thu, May 2, 2013 at 3:29 PM, Ramsay Jones <ramsay@ramsay1.demon.co.uk> wrote:
> Commit 380a4d92 ("Update cygwin.c for new mingw-64 win32 api headers",
> 11-11-2012) solved an header include order problem on cygwin 1.7 when
> using the new mingw-64 WIN32 API headers. The solution involved using
> a new build variable (V15_MINGW_HEADERS) to conditionally compile the
> cygwin.c source file to use an include order appropriate for the old
> and new header files. (The build variable was later renamed in commit
> 9fca6cff to CYGWIN_V15_WIN32API).
>
> The include order used for cygwin 1.7 includes the "win32.h" header
> before "../git-compat-util.h". This order was problematic on cygwin
> 1.5, since it lead to the WIN32 symbol being defined along with the

s/lead/led/

> inclusion of some WIN32 API headers (e.g. <winsock2.h>) which cause
> compilation errors.
>
> The header include order problem on cygwin 1.5 has since been fixed
> (see commit "mingw: rename WIN32 cpp macro to GIT_WINDOWS_NATIVE"),
> so we can now remove the conditional compilation along with the
> associated CYGWIN_V15_WIN32API build variable.
>
> Signed-off-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>

      reply	other threads:[~2013-05-03  8:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 19:29 [PATCH v2 2/2] cygwin: Remove the CYGWIN_V15_WIN32API build variable Ramsay Jones
2013-05-03  8:17 ` Eric Sunshine [this message]

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='CAPig+cR3s4nzSOrG+=-MYEA4heTeMHpHQmAChWLEuFY2v+PhPA@mail.gmail.com' \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=mlevedahl@gmail.com \
    --cc=ramsay@ramsay1.demon.co.uk \
    /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).