From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin-64 on W10-64 : the only game in town?
Date: Sun, 1 Nov 2020 09:51:56 -0700 [thread overview]
Message-ID: <a214df57-d50a-74bc-0941-6b8634798ea7@SystematicSw.ab.ca> (raw)
In-Reply-To: <CANnLRdh9Npgsw2eSdutUJd+2xVtW23bsbCnUx_42Cz=MdRkCmQ@mail.gmail.com>
On 2020-11-01 08:20, Stephen John Smoogen via Cygwin wrote:
> On Sun, 1 Nov 2020 at 04:02, Duncan Roe wrote:
>> On Sun, Nov 01, 2020 at 08:49:23AM +0000, Fergus Daly wrote:
>>> With W7 no longer supported, W10-32 supported but no longer provided on
>>> new machines (Microsoft states that, "Beginning with Windows 10, version
>>> 2004, all new Windows 10 systems will be required to use 64-bit builds
>>> and Microsoft will no longer release 32-bit builds for OEM distribution
>>> .. the weaker version of Windows 10 has several limitations, like
>>> capping out at 3.2GB of RAM and less stringent security measures") and
>>> the functionality of Cygwin-32 significantly downplayed on Cygwin's own
>>> Home page, that really does leave Cygwin-64 on W10-64 on 64-bit hardware
>>> as the sole recommended platform. Yes?
Cygwin64 is the recommended release, there are no recommended platforms,
although there are minimum requirements for the code to run, and to build the
code: if you can run it under ReactOS on an old Pentium, good on you! ;^>
>> No, I run Cygwin64 on Win 7. There is an outstanding W7 update, it appeared
>> a few weeks ago, but I'm not taking it.
> The question is nuanced around "what is the recommended platform". Now as
> individuals we can recommend anything we want if it works for us.. but we
> also aren't expecting to answer all of Fergus's questions when he tries to
> get Cygwin working on his system. I think in the end, for the project, the
> recommendation would be whatever Corinna recommends as she is the primary
> author of the code these days and the one who would be fixing problems
> found.
That has been determined in the past by the need in a new Wdindows release,
version, or edition, to use a new API, that may not be avoided or skipped for
the oldest versions in a backward-compatible way, as happened when support for
new versions had to be added, so XP support had to be dropped.
--
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.]
next prev parent reply other threads:[~2020-11-01 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 8:49 Fergus Daly
2020-11-01 9:00 ` Duncan Roe
2020-11-01 11:23 ` Hamish McIntyre-Bhatty
2020-11-01 15:20 ` Stephen John Smoogen
2020-11-01 16:51 ` Brian Inglis [this message]
2020-11-02 9:13 ` Corinna Vinschen
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=a214df57-d50a-74bc-0941-6b8634798ea7@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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).