From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Cc: Arash Esbati <arash@gnu.org>
Subject: Re: Support for MS-Windows build of Emacs (was: Warnings during building the current master on Win10 with MSYS2/MinGW64)
Date: Thu, 25 Jul 2024 08:52:39 +0300 [thread overview]
Message-ID: <86plr2587s.fsf@gnu.org> (raw)
In-Reply-To: <86jzha4kc3.fsf@gnu.org> (message from Arash Esbati on Wed, 24 Jul 2024 22:16:12 +0200)
> From: Arash Esbati <arash@gnu.org>
> Date: Wed, 24 Jul 2024 22:16:12 +0200
>
> after a long time, I built Emacs (baf9f1210a) from master on my Win10
> box and it occurred to me that I get more warnings than I used to. This
> is with
>
> $ gcc --version
> gcc.exe (Rev3, Built by MSYS2 project) 14.1.0
Sadly, the MS-Windows port of Emacs is basically not taken care of
anymore. There are no active developers on board who seem to care
about it, except yours truly. I see this in the (lack of) responses
to Windows-specific bugs and issues reported to the bug tracker: no
one chimes in, even if I deliberately leave a bug report without
responses for many days. As my free time is severely limited, I only
care about aspects that affect me directly (and the 64-bit build and
GCC 14 are way outside that scope).
If no one comes forward and starts taking care of the MS-Windows
issues, I'm very close to the decision of declaring the Windows build
of Emacs "unsupported", meaning anyone who needs it are "on their
own", from my POV as the (co)maintainer.
This is not an April 1 joke: if there's a significant community
interested in being able to run and develop Emacs on MS-Windows,
someone should volunteer to take care of the build on a day to day
basis, or else the conclusion is that there's no general interest in
that platform among the Emacs community that is high enough to justify
the investment.
You _have_ been warned!
next prev parent reply other threads:[~2024-07-25 5:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 20:16 Warnings during building the current master on Win10 with MSYS2/MinGW64 Arash Esbati
2024-07-25 5:52 ` Eli Zaretskii [this message]
2024-07-25 11:03 ` Support for MS-Windows build of Emacs Arash Esbati
2024-07-25 11:38 ` Po Lu
2024-07-28 2:58 ` Richard Stallman
2024-07-30 14:30 ` Arash Esbati
2024-07-30 16:03 ` Eli Zaretskii
2024-07-30 16:34 ` Juergen Fenn
2024-07-29 14:13 ` Support for MS-Windows build of Emacs (was: Warnings during building the current master on Win10 with MSYS2/MinGW64) Tom Davey
2024-07-25 5:56 ` Warnings during building the current master on Win10 with MSYS2/MinGW64 Eli Zaretskii
2024-07-25 6:49 ` Collin Funk
2024-07-25 11:11 ` Arash Esbati
-- strict thread matches above, loose matches on Subject: below --
2024-08-05 16:48 Support for MS-Windows build of Emacs (was: Warnings during building the current master on Win10 with MSYS2/MinGW64) Kepa
2024-08-05 17:41 ` Eli Zaretskii
2024-08-05 20:49 ` Kepa
2024-08-06 0:02 ` Corwin Brust
2024-08-06 11:38 ` Eli Zaretskii
2024-08-06 15:27 ` Corwin Brust
2024-08-06 11:25 ` Eli Zaretskii
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=86plr2587s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arash@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.