bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: "bug-gnulib@gnu.org" <bug-gnulib@gnu.org>,
	Bruno Haible <bruno@clisp.org>
Subject: Adding Cygwin and MSYS2 to DEPENDENCIES
Date: Wed, 1 May 2024 16:48:18 -0700	[thread overview]
Message-ID: <9a7c7aad-5c8d-4149-a867-8fed79025326@gmail.com> (raw)

Hi Bruno,

Before I add Cygwin and MSYS2 to the DEPENDENCIES file can you double
check them?

I don't want to add too much detail to that file, but it is my
understanding that MSYS2 is meant for building native Windows
software. Cygwin is more of a runtime environment, though it has MinGW
packages for building native Windows software. Am I understanding this
correctly?

I put "Recommended" since most users will not need to worry about
this. For Windows, these are just the best ways to avoid the headaches
caused by that platform.

Any changes that I should make before pushing?

diff --git a/DEPENDENCIES b/DEPENDENCIES
index b700c05bc6..066becbc98 100644
--- a/DEPENDENCIES
+++ b/DEPENDENCIES
@@ -197,3 +197,22 @@ at any time.
     https://www.gnu.org/software/tar/
   + Download:
     https://ftp.gnu.org/gnu/tar/
+
+* Cygwin
+  + Recommended.
+    Provides a POSIX-like environment and binary packages necessary to
+    build and run software on Windows. Native Windows programs can be
+    compiled using a MinGW toolchain.
+  + Homepage:
+    https://cygwin.com/
+  + Download:
+    https://cygwin.com/install.html
+
+* MSYS2
+  + Recommended.
+    Provides a shell and binary packages necessary to build and run
+    software on native Windows.
+  + Homepage:
+    https://www.msys2.org/
+  + Download:
+    https://www.msys2.org/#installation

Collin


             reply	other threads:[~2024-05-01 23:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 23:48 Collin Funk [this message]
2024-05-02  0:35 ` Adding Cygwin and MSYS2 to DEPENDENCIES Bruno Haible
2024-05-02  1:31   ` Collin Funk
2024-05-02  9:29     ` Bruno Haible
2024-05-02 21:34       ` Collin Funk
2024-05-02 22:28         ` Bruno Haible
2024-05-02 22:44           ` Collin Funk
2024-05-02 22:50             ` Bruno Haible
2024-05-02 22:57               ` Collin Funk

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a7c7aad-5c8d-4149-a867-8fed79025326@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    /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).