all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: "David M. Miller" <dmmiller2k@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Windows emacs-25.1 i686 vs x86_64?
Date: Thu, 03 Nov 2016 16:28:54 +0000	[thread overview]
Message-ID: <87mvhgsf21.fsf@russet.org.uk> (raw)
In-Reply-To: <b361e3a3-849e-486a-b758-64316c0efea5@googlegroups.com> (David M. Miller's message of "Thu, 3 Nov 2016 09:00:42 -0700 (PDT)")

"David M. Miller" <dmmiller2k@gmail.com> writes:

> On Thursday, November 3, 2016 at 11:32:42 AM UTC-4, David M. Miller wrote:
>> When I went to download 25.1 for windows I saw two packages on the main GNU ftp server:
>> 
>>     emacs-25.1-i686-w64-mingw32.zip
>>      - AND -
>>     emacs-25.1-x86_64-w64-mingw32.zip
>> 
>> but no explanation of the difference between them in the README file.
>> 
>> Also, there seems to be a separate package of "deps" for each:
>> 
>>     emacs-25-i686-deps.zip
>>      - AND -
>>     emacs-25-x86_64-deps.zip
>> 
>> the need for which is also not explained anywhere (dependencies? dependencies for what?).
>> 
>> Does anyone know what the difference between the i686 and x86_64 packages are?
>> Does anyone know what the "deps" packages are for?
>> 
>> Thanks,
>> David
>
> After examining both main emacs packages, I think I figured out the obscure
> naming conventions: 'i686' refers to the 32-bit version, while 'x86_64' refers
> to the 64-bit version. So this answers my first question.
>
> I have no intention of doing so, but I still wonder whether the "deps" package
> is intended for *BUILDING* emacs, or if it provides runtime binary support for
> some of the more obscure elisp facilities.


Apologies for this. I built those packages, and haven't got around to
updating the README. I will try and do so tonight.

i686 and x86_64 are the 32 and 64 bit versions respectively. The names
come from the names for these platforms used in ./configure. Probably
not something that I should be inflicting on users. The "deps" package
are the external dependencies that Emacs uses, for features like XML
parsing, image rendering and so forth. If you unpack these over the
relevant version of Emacs, it's powers will be magically enhanced.

Phil



  parent reply	other threads:[~2016-11-03 16:28 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 15:32 Windows emacs-25.1 i686 vs x86_64? David M. Miller
2016-11-03 15:39 ` tomas
2016-11-03 16:00 ` David M. Miller
2016-11-03 16:26   ` John Mastro
2016-11-03 16:28   ` Phillip Lord [this message]
2016-11-03 17:44     ` David M. Miller
2016-11-03 22:21       ` Phillip Lord
2016-11-03 17:58     ` Eli Zaretskii
2016-11-03 22:25       ` Phillip Lord
2016-11-04  7:19         ` Eli Zaretskii
2016-11-04 10:19           ` Phillip Lord
2016-11-05  8:16             ` Eli Zaretskii
2016-11-05 22:26               ` Phillip Lord
2016-11-06  3:43                 ` Eli Zaretskii
2016-11-06  8:10                   ` Paul Eggert
2016-11-06 15:48                     ` Eli Zaretskii
2016-11-06 16:13                       ` Óscar Fuentes
2016-11-06 16:43                         ` Eli Zaretskii
2016-11-06 17:01                           ` Óscar Fuentes
2016-11-06 17:24                             ` Eli Zaretskii
2016-11-06 18:26                               ` Óscar Fuentes
2016-11-06 18:42                                 ` Eli Zaretskii
2016-11-06 19:17                                 ` Eli Zaretskii
2016-11-06 20:15                                   ` Óscar Fuentes
2016-11-07 14:40                             ` Richard Stallman
2016-11-07 15:16                               ` Phillip Lord
2016-11-08 13:53                                 ` Richard Stallman
2016-11-06 16:51                       ` Stefan Monnier
2016-11-06 18:50                       ` John Wiegley
2016-11-07 14:42                         ` Richard Stallman
2016-11-06 21:54                       ` Paul Eggert
2016-11-06 21:57                         ` Daniel Colascione
2016-11-07 14:43                         ` Richard Stallman
2016-11-07 15:15                           ` Daniel Colascione
2016-11-07 15:26                           ` Phillip Lord
2016-11-08 13:53                             ` Richard Stallman
2016-11-08 14:52                               ` Phillip Lord
2016-11-08 15:31                                 ` Eli Zaretskii
2016-11-09 16:50                                   ` Phillip Lord
2016-11-09 17:15                                     ` Eli Zaretskii
2016-11-09 17:18                                     ` Stefan Monnier
2016-11-10 15:19                                       ` Phillip Lord
2016-11-09  7:00                                 ` martin rudalics
2016-11-15 10:26                                 ` Phillip Lord
2016-11-07 16:34                           ` Paul Eggert
2016-11-07 18:07                             ` Eli Zaretskii
2016-11-07 19:02                               ` Perry E. Metzger
2016-11-07 19:29                                 ` Eli Zaretskii
2016-11-07 21:54                                   ` Phillip Lord
2016-11-07 19:39                                 ` Stefan Monnier
2016-11-07 20:02                                   ` Perry E. Metzger
2016-11-07 20:10                                     ` Stefan Monnier
2016-11-07 20:22                                       ` Perry E. Metzger
2016-11-07 20:27                                         ` Eli Zaretskii
2016-11-08  3:48                                           ` Elias Mårtenson
2016-11-08 15:32                                             ` Eli Zaretskii
2016-11-07 18:49                           ` Perry E. Metzger
2016-11-08 13:55                             ` Richard Stallman
2016-11-08 14:34                               ` Perry E. Metzger
2016-11-06 21:50                   ` Phillip Lord
2016-11-06  4:13                 ` Noam Postavsky

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=87mvhgsf21.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=dmmiller2k@gmail.com \
    --cc=help-gnu-emacs@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.