> -----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? > > -- > Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada > > This email may be disturbing to some readers as it contains > too much technical detail. Reader discretion is advised. > [Data in binary units and prefixes, physical quantities in SI.] -- Jason Pyeron | Architect PD Inc | Certified SBA 8(a) 10 w 24th St | Certified SBA HUBZone Baltimore, MD | CAGE Code: 1WVR6 .mil: jason.j.pyeron....@mail.mil .com: jpye...@pdinc.us tel : 202-741-9397
