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 *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. That too, as well as the mingw64-*-headers used in the MinGW-w64 toolchain. > 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. I suppose so for Cygwin, but the mingw64-*-headers could be different. > 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. Fair enough. -- Yaakov -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple