public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Default mingw _WIN32_WINNT
Date: Tue, 5 May 2020 10:54:36 +0200	[thread overview]
Message-ID: <20200505085436.GC3947@calimero.vinschen.de> (raw)
In-Reply-To: <CALK-3m+s1ZaBq1L2yHj1aVZbps98X+sQrHJATmfJEQ4oLenBOA@mail.gmail.com>

On May  5 08:45, Biswapriyo Nath via Cygwin wrote:
> Chaging the defines in package may break others installation.

No, it doesn't in this case.

Yaakov is talking about mingw-w64 headers used to create *Cygwin*
applications using the occasional Windows function.  Cygwin executables
in the distro run on Vista but not on XP or 2K3 anymore, given the
Cygwin DLL doesn't.

Therefore it might be a good idea to bump the default for these
Cygwin-related headers to at least 0x0600.

Setting them to 0x0602 sounds like a good idea, but as long as we didn't
drop Vista or W7 support it might be premature.

Btw., checking Cygwin sources for Vista and W7-specific code, it turned
out that actually very few lines of code handle Vista or W7-specific
workarounds.  The advantage of removing the code is pretty minor, so I
didn't push the changes.  While it's a bad idea to keep Vista and W7
running (at least attached to the internet), we can support them a while
longer.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

  reply	other threads:[~2020-05-05  8:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 21:42 Yaakov Selkowitz
2020-05-05  3:15 ` Biswapriyo Nath
2020-05-05  8:54   ` Corinna Vinschen [this message]
2020-05-05  9:05     ` Rainer Emrich
2020-05-05 10:06       ` JonY
2020-05-05 10:11         ` Corinna Vinschen
2020-05-11 14:55       ` Chris Wagner
2020-05-11 16:53         ` Yaakov Selkowitz
2020-05-11 23:08           ` Chris Wagner
2020-05-08  0:33     ` Yaakov Selkowitz
2020-05-08  9:29       ` Corinna Vinschen

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=20200505085436.GC3947@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).