unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Layer <layer@known.net>
To: Phillip Lord <phillip.lord@russet.org.uk>
Cc: emacs-devel@gnu.org
Subject: Re: Are there non-mingw32 binaries for Windows?
Date: Thu, 17 Nov 2016 09:54:55 -0800	[thread overview]
Message-ID: <CAGSZTjLVv4TtGb7tYYGr3rkHujvyF0uxzU2ch_998W=sXP_iOA@mail.gmail.com> (raw)
In-Reply-To: <5c2aca208090e22a5029d348fe2206bb.squirrel@cloud103.planethippo.com>

I've just never used the mingw32 binaries and the installation is more
complex.  I have been repackaging the older, single-zip binaries with
an NSIS installer, since it's just easier for Windows people to run an
exe to install.  The NSIS installer is here:

https://github.com/franzinc/emacsinstaller/

I'm just embarking on the task of updating it for 25.1, and wanted to
know if the old style binaries were just temporarily missing or gone
forever.  So, it's the latter.  I'll work to modify the scripts.

One question about the mingw32 emacs binary: is it like the Cygwin
emacs binary where it uses Cygwin mounts?  What I liked about the
native (MSVC) compiled emacs was that it used C:\... instead of /c/...

Thanks.

Kevin

On Thu, Nov 17, 2016 at 6:58 AM, Phillip Lord
<phillip.lord@russet.org.uk> wrote:
> 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
>



  reply	other threads:[~2016-11-17 17:54 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
2016-11-17 17:54   ` Kevin Layer [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to='CAGSZTjLVv4TtGb7tYYGr3rkHujvyF0uxzU2ch_998W=sXP_iOA@mail.gmail.com' \
    --to=layer@known.net \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).