X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9C953385DC1B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1588930218; bh=A15IqD01X3Suf6Uud6g6GjttPRw9Wt7BimYY/mfCB94=; h=Date:From:To:Subject:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Reply-To:From; b=kbv7mJ0gXJQisYEegPmNYivPYVl6aR4JNlgmyUoRV8OeDIyfohBLis7ZfxKjrN8q0 SdnvBxYT3CcoM//z5soNyYW+zPq8Kwqlfzj0OB6OAyyJWewlUQ8fxY5Y3QSAp6LDh/ lWDCxJ4SyiWpCrSbspCexRbbGpG5IopwYN+RBLjQ= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 15B7A385DC1B Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cygwin.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=corinna-cygwin AT cygwin DOT com Date: Fri, 8 May 2020 11:29:59 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Default mingw _WIN32_WINNT Message-ID: <20200508092959.GH3947@calimero.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: <7101b829ec197e48e3aaf373625d950e95e29df4 DOT camel AT cygwin DOT com> <20200505085436 DOT GC3947 AT calimero DOT vinschen DOT de> <95f068fab863e88dfe99734834e00af73a13d64a DOT camel AT cygwin DOT com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <95f068fab863e88dfe99734834e00af73a13d64a.camel@cygwin.com> X-Provags-ID: V03:K1:r9ZS7Ds9P3RKQknvEpTB/UMGi17PwRKqVeeCnuW1XABkIXuuKq6 qMmX89sBRDC4HmFluQ3s+SnHd7bnVdV8UU/4XEkA+SSa1z8nR3B3tcRnYJK+ljbJuUbirOS YlTEMDZUhzO0hQoonP3Ff6jeU4xLCchdMyfT08LF+ulJ12bWFB3D2guNF/sEN9uLAhkUEdn GUteXRbHhbPxL0e6MeoNQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:XYZW3v9gnnU=:QmGbmtM2KLHUmeiG9vJP2M iehFo5jYCYJt7GBgARY9FhDe3NaBq4PDbL0B7BHE7Ns/78XuOyA7MCIYznEqY3rbgKv4VVM8x tEtaDU1y3OBSVx5yxH6dX0qBPm5+Zp2XDVSqogyrpW+5DK8s+aNbcTmv+HdzWwbb/zWXTiwVW EMHJzQqkyUe1lt4oSBiBWPPX7BZg6EK7uvYJsOElsobAPjdH3+n5sogXAZBTky/zwBD94SW89 wh29I2hH6EQBRpn7/ofNO768dnnhZ4T1d+nLcWXl4xPWsREVd4/F3lAwiModbMe7CkgmcH8xm s6T71kMrxreFVD/N+O6AfJ1zRCJKc8EnY61+zKecRRjO1PuDl2ysCFKRDRUyExuiJgAyFlIe0 z10TZOXfHtQiNWRjI2a6bEd8TSee5gbwy987VqFqRgoeUkJgvCVezuz2jnl8lASsDamJ1xAnj YomxLDIk3ASiNGkHoDsTPVcXk2402A0FbfvlORadO6NxtaJR2dF1vhAT6No4IPv+zaHlsDfr7 7Yd6Un9B4zrzxdl8IlEZHTJqfjV9Sl9V8CuOTD5YPxg9QdZOST8VERtPZ198TpJR/4NEMpd5r ibDOm3OtMmBbzyJHtzx48O/ELM/MxSuKrVBkgXdpsJZSVWPaGXc6XvlZCbQ0h+ipA6J9n/8sA rZ9YMSDgXvjK6yGfNlyt0G6IOzA2DeGaHzZbjQqaXYOE0X/jR06uwEUylGLoffdCiRPOBsF+e CIC4jjMG37FH/SrF4qGl+A82RguNGcecvMtPowCuMYRBXkYs3PDXNWX+bBxjKlVy/Fu/JZqBU bvQRnBae1ZxDp1ZivifJ1+3L5ouheyTHvcEb5khSRWzC41AXUdlmYViKeFRODcH3DWwsjVo X-Spam-Status: No, score=-98.3 required=5.0 tests=BAYES_00, GOOD_FROM_CORINNA_CYGWIN, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NEUTRAL, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: cygwin AT cygwin DOT com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" 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: Creating Cygwin executables Case 2: Creating native executables In case 1, setting _WIN32_WINNT to 0x0600 just follows reality in that Cygwin executables don't run on pre-Vista anymore, so using Win32 functions from same executables follows the same rule. In case 2, it's a legitimate goal to create executables still running on older versions of Windows. In how far changing _WIN32_WINNT makes sense or not for native development doesn't actually belong here, it would have to be discussed on the mingw-w64 mailing lists. > > 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. I disagree, see above. > > 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. No, the mingw headers for Cygwin are mainly targeted at building Cygwin executables additionally using Win32 functions, and these are runing on 0x0600 or later. The fact that Cygwin is developed using the same set of headers doesn't really matter for this. Corinna -- Corinna Vinschen Cygwin Maintainer -- 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