From: "Jason Pyeron" <jpyeron@pdinc.us>
To: "Kyle Marek" <kmarek@pdinc.us>
Cc: <cygwin-apps@cygwin.com>
Subject: RE: Dropping various support in future releases - what about Mingw?
Date: Sun, 31 Oct 2021 19:06:55 -0400 [thread overview]
Message-ID: <663801d7ceac$00283210$00789630$@pdinc.us> (raw)
In-Reply-To: <d4f33cdb-08fc-ae12-b0cd-f60f0d2a12a8@SystematicSw.ab.ca>
> -----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.ctr@mail.mil
.com: jpyeron@pdinc.us
tel : 202-741-9397
next prev parent reply other threads:[~2021-10-31 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 15:23 Brian Inglis
2021-10-31 23:06 ` Jason Pyeron [this message]
2021-11-01 17:33 ` Kyle Marek
2021-11-01 16:27 ` Achim Gratz
2021-11-01 18:47 ` Brian Inglis
2021-11-01 19:33 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='663801d7ceac$00283210$00789630$@pdinc.us' \
--to=jpyeron@pdinc.us \
--cc=cygwin-apps@cygwin.com \
--cc=kmarek@pdinc.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).