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 12:11:18 +0200	[thread overview]
Message-ID: <20200505101118.GD3947@calimero.vinschen.de> (raw)
In-Reply-To: <2bd7e94d-e6e8-be8f-f409-c78ecf0aa643@gmail.com>

On May  5 10:06, JonY via Cygwin wrote:
> On 5/5/20 9:05 AM, Rainer Emrich wrote:
> > Hi Corinna,
> > 
> > Am 05.05.2020 um 10:54 schrieb Corinna Vinschen:
> >> 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.
> > I would expect support for Windows 7 as long as the Micsrosoft ESU
> > program is active.
> > 
> 
> By right, applications needing newer APIs should be setting them instead
> of relying on the defaults. In this case, Cygwin compiled with
> -D_WIN32_WINNT=0x602 if needed.

It's not about compiling Cygwin itself (which sets _WIN32_WINNT to
0x0a00 anyway), it's about compiling executables *for* Cygwin.  Given
they won't run under pre-0x0600 anyway, it may be a good thing if the
win32 headers for Cygwin executables define the minimum possible as
default.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

  reply	other threads:[~2020-05-05 10:11 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
2020-05-05  9:05     ` Rainer Emrich
2020-05-05 10:06       ` JonY
2020-05-05 10:11         ` Corinna Vinschen [this message]
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=20200505101118.GD3947@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).