public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: Quick query about Windows versions
Date: Wed, 1 Apr 2020 14:14:47 +0200	[thread overview]
Message-ID: <d5b633e2-4679-2357-b94c-b1dd18cc654e@towo.net> (raw)
In-Reply-To: <20200401093608.GW3261@calimero.vinschen.de>

Am 01.04.2020 um 11:36 schrieb Corinna Vinschen:
> On Mar 31 18:58, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 31/03/2020 17:24, ASSI wrote:
>>> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>>>> Just thought I should ask: is there a perferred version of Windows to
>>>> build packages on, or does it not matter?
>>> Whatever supported version of Windows you use, I'd say.
>>>
>>>> I currently build on Windows 7, following the tradition of building on
>>>> the oldest supported platform, but I have no idea if this is needed with
>>>> Cygwin.
>>> No Windows 7 system should still have the ability to connect to the
>>> internet… so no, I don't think you should even try to build there.
>>>
>>>
>>> Regards,
>>> Achim.
>> Yep, that's why I asked. I'll upgrade the VM to Windows 10 then, if it
>> makes no difference to Cygwin.
> None at all.  Right now we still support all versions since Windows
> Vista, so any breakage building stuff on these systems is the fault
> of the Cygwin core.  Other than that, Achim is right, of course :)
Unless your package would use w32api and explicitly detect the build 
system version to include more or less features depending on it...

  reply	other threads:[~2020-04-01 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 14:15 Hamish McIntyre-Bhatty
2020-03-31 16:24 ` ASSI
2020-03-31 17:58   ` Hamish McIntyre-Bhatty
2020-04-01  9:36     ` Corinna Vinschen
2020-04-01 12:14       ` Thomas Wolff [this message]
2020-04-01 17:29         ` Corinna Vinschen
2020-04-01 13:59       ` Hamish McIntyre-Bhatty

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=d5b633e2-4679-2357-b94c-b1dd18cc654e@towo.net \
    --to=towo@towo.net \
    --cc=cygwin-apps@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).