From: "Phillip Lord" <phillip.lord@russet.org.uk>
To: "Kevin Layer" <layer@known.net>
Cc: emacs-devel@gnu.org
Subject: Re: Are there non-mingw32 binaries for Windows?
Date: Thu, 17 Nov 2016 14:58:03 -0000 [thread overview]
Message-ID: <5c2aca208090e22a5029d348fe2206bb.squirrel@cloud103.planethippo.com> (raw)
In-Reply-To: <CAGSZTjL+TTQqWK-qU9Nn2rdLt3ji33ghFyrY0ixDbXO+F+p-6g@mail.gmail.com>
On Wed, November 16, 2016 11:47 pm, Kevin Layer wrote:
> It seems 24.3 was the last version that had non-mingw32 binaries. I'm
> speaking of this:
>
> https://ftp.gnu.org/gnu/emacs/windows/emacs-24.3-bin-i386.zip
>
>
> Is there an equivalent build like this for 25.1?
Both builds (32 and 64 bit) for 25.1 use mingw.
I'd like to unpick a bit why you are asking the question, because it may
mean that our documentation or file naming is confusing.
Are you looking for a "standalone" emacs that can be installed without a
mingw or msys2 installation? If that is the case, the binaries provided
will do this job for you.
Are you worried about the altered directory structure (i.e. /var, /bin,
/etc)?
Do you have some other reason for not using ming compiled binaries?
Probably for future releases of windows binaries, I should drop the
"-ming" from the file name. It's not doing anything.
Phil
next prev parent reply other threads:[~2016-11-17 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 23:47 Are there non-mingw32 binaries for Windows? Kevin Layer
2016-11-17 1:08 ` Óscar Fuentes
2016-11-17 3:38 ` Eli Zaretskii
2016-11-17 7:16 ` Fabrice Popineau
2016-11-17 14:58 ` Phillip Lord [this message]
2016-11-17 17:54 ` Kevin Layer
2016-11-17 19:36 ` Óscar Fuentes
2016-11-17 20:41 ` Eli Zaretskii
2016-11-17 21:46 ` Kevin Layer
2016-11-18 19:28 ` Richard Copley
2016-11-20 21:24 ` Phillip Lord
2016-11-21 0:18 ` Richard Copley
2016-11-21 20:56 ` Phillip Lord
2016-11-20 21:21 ` Phillip Lord
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=5c2aca208090e22a5029d348fe2206bb.squirrel@cloud103.planethippo.com \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=layer@known.net \
/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.