On 2020-05-11 12:53 pm, Yaakov Selkowitz wrote:
I would just like to chime in that it would be a crying shame if
Cygwin
were to ever drop support for Windows 7. There are many people,
myself
one, who are dead set against Windows 10.
"Ever"?!? You do realize that, ESU aside, Windows 7 is out
On Mon, 2020-05-11 at 10:55 -0400, Chris Wagner wrote:
> On 2020-05-05 5:05 am, Rainer Emrich wrote:
> > 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
On 2020-05-05 5: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 Vi
On May 7 20:33, Yaakov Selkowitz wrote:
> On Tue, 2020-05-05 at 10:54 +0200, Corinna Vinschen wrote:
> > 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.
>
> In what case would it?
Case 1:
On Tue, 2020-05-05 at 10:54 +0200, Corinna Vinschen wrote:
> 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.
In what case would it?
> Yaakov is talking about mingw-w64 headers used to create *Cy
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
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
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
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 r
Chaging the defines in package may break others installation. You can set
the version in source code as you need, for example:
#undef _WIN32_WINNT
#define _WIN32_WINNT 0x602
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:
JonY,
In w32api-headers and mingw64-*-headers, the default value of
_WIN32_WINNT can be configured at build-time with --with-default-win32-
winnt=$VER, with the default still being 0x502 (XP x64/2003 R2). With
2008, 2008 R2, and 7 having gone out of support earlier this year,
Server 2012 is now t
11 matches
Mail list logo
