From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.pdinc.us (mail2.pdinc.us [67.90.184.28]) by sourceware.org (Postfix) with ESMTPS id D306C3858403 for ; Mon, 1 Nov 2021 17:33:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D306C3858403 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=pdinc.us Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=pdinc.us Received: from localhost (cpe-173-88-170-197.neo.res.rr.com [173.88.170.197]) (authenticated bits=0) by mail2.pdinc.us (8.14.4/8.14.4) with ESMTP id 1A1HXe7g017681 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Mon, 1 Nov 2021 13:33:41 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 mail2.pdinc.us 1A1HXe7g017681 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pdinc.us; s=default; t=1635788021; bh=anA13YoIWzuJ80EH4qctWjzs9eZOwcbo533mfIoZiZ8=; h=Subject:To:References:From:Date:In-Reply-To:From; b=puMiINpdWxQBUjE2NGhBGQ8F0y0jBlqIqOtQjn/kMIAdCJaCr9I1aNiXre/N6wWTx ZJYg02wDWR1C704fklRMckrqzG3zRo4Sya9HMkagBWXaQsXxfKqqT2Z2TRr83+qdos t9SJa+Yga4A7E2mJSfx84qOIw20HyrZsMCb87WZCiwv8bWBxRRBZwWS94TppR/DSXX vAyer4Dwg3BVqwoCA+zeAgpomgjpf51YUthPdRjVHinYArdY0TiLudD4Kq2097JVRz nCB3XN6Bua7lkvOYikKhr4fLbspdy7WzRl/LQTCJaCNuYVv0GjTfl/uijYdJPsu5CR GNSj4eaeK450w== Subject: Re: Dropping various support in future releases - what about Mingw? To: Jason Pyeron , cygwin-apps@cygwin.com References: <663801d7ceac$00283210$00789630$@pdinc.us> From: Kyle Marek Message-ID: <08b7adc4-0c36-ac83-fb6c-9a4d8626d0d7@pdinc.us> Date: Mon, 1 Nov 2021 13:33:40 -0400 User-Agent: Mozilla/5.0 (X11; Linux ppc64le; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <663801d7ceac$00283210$00789630$@pdinc.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_ASCII_DIVIDERS, KAM_INFOUSMEBIZ, NICE_REPLY_A, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2021 17:33:44 -0000 On 10/31/21 7:06 PM, Jason Pyeron wrote: >> -----Original Message----- >> From: Brian Inglis >> Sent: Sunday, October 31, 2021 11:23 AM >> >> Perhaps someone could explain why Cygwin maintains, builds, and >> distributes Mingw tools and libraries, instead of that being done by the >> Mingw project(s) about which I know little? >> >> As we will be dropping Windows versions and 32 bit support in future >> releases, should we also be looking at dropping the Mingw packages we >> maintain, build, and distribute, but do not appear to use, except for >> building other Mingw packages? >> >> Supporting the two Mingw variations on packages sometimes takes as much >> work as the Cygwin packages, as parts of the toolchains and libraries >> may have different versions and dependencies. >> >> I basically build, check, and distribute those, but know little about >> using them to check they work, so no idea whether they work or not. >> >> I have had little success in getting the Mingw dual arch build process >> working to any useful extent, and no response to questions about that, >> which I may have buried at the end of my other verbiage on this list. > Kyle, > > Thoughts? Being a GCC toolchain, MinGW *could* distribute binaries built with MinGW itself (such that they do not depend in Cygwin or MSYS). However, MinGW doesn't have a package manager that would allow developers to easily add development libraries besides the usual msvcrt symbol stubs and libstdc++ or whatever, so I wouldn't necessarily say that they *should* distribute binaries themselves. On the 32-bit support issue: regardless of Cygwin dropping support for 32-bit, and regardless of Cygwin's own use of MinGW to build setup.exe (as Achim pointed out), MinGW is used as a cross-compiler for developers to target 32-bit non-Cygwin platforms. There is value in Cygwin being useful on modern machines as a development environment to target older platforms, even if Cygwin itself won't run on older platforms. Obviously this might be a minority use case and Cygwin is a volunteer project, so it would be understandable if the 32-bit cross compiler packages went away due to a lack of volunteer interest. I hope this doesn't happen, because it is not really fun to compile our own cross-compilers. I am not a Cygwin package maintainer, so I have no opinions regarding package maintenance. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Kyle Marek PD Inc. http://www.pdinc.us - - Jr. Developer 10 West 24th Street #100 - - +1 (443) 269-1555 x361 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-