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: Arash Esbati <arash.esbati@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs binaries for Windows
Date: Fri, 19 Aug 2016 16:03:04 +0100	[thread overview]
Message-ID: <877fbc3ion.fsf@russet.org.uk> (raw)
In-Reply-To: <86mvk9jj6i.fsf@gmail.com> (Arash Esbati's message of "Fri, 19 Aug 2016 09:45:41 +0200")

Arash Esbati <arash.esbati@gmail.com> writes:
> I know this topic has been discussed in past and my apologies in advance
> if I'm beating the dead horse again and a longish message.

It's not a dead horse at all. It's an issue which, to my mind, needs
solving.

> I'm raising this question after seeing some queries again about
> availability of Emacs on Windows (possibly incl. all necessary
> libraries (DLLs)).
>
> While building Emacs on Windows with Msys2/MinGW-w64 is quite straight
> forward, the main issue is providing the sources of the libraries when
> DLLs should be provided as well.  I wrote a simple script to determine
> the dependencies of the required packages mentioned here:
>
>     http://git.savannah.gnu.org/cgit/emacs.git/tree/nt/INSTALL.W64#n60


I'd be interested to see this script.


> It downloads the original sources mentioned in every PKGBUILD file and
> includes patches from here:
>
>     https://github.com/Alexpux/MINGW-packages
>
> Is this a way to go for Emacs?


> Personally, I recommend another approach where only Msys2 package
> directories (which Emacs was built against) are provided and downloading
> and packaging can be done when a developer/user wants to have it, e.g.:
>
>     cd mingw-w64-bzip2
>     makepkg-mingw --allsource -sLf
>
> This is actually what my script does.  Collecting all directories for
> the packages above gives:
>
>     -> du -h emacs-25.1-rc1-libs.tar.xz
>     464K    emacs-25.1-rc1-libs.tar.xz
>
> Does this approach comply with GPL?


I don't know enough about msys2 to understand the difference in your
approaches, but AFAICT, -libs.tar.xv contains all the source, so that
you could build the libraries, then it does, yes.

At the moment, Emacs ships with a single binary (libnox4) otherwise it
looks terrible. But, I think that the basic windows download cannot do
an HTTP call and display the results is unfortunate.

Current builds are for 32 bit as well as 64 bit. Can that be replicated
also?

Phil



  parent reply	other threads:[~2016-08-19 15:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  7:45 Emacs binaries for Windows Arash Esbati
2016-08-19 14:50 ` Eli Zaretskii
2016-08-19 16:33   ` Arash Esbati
2016-08-19 17:51     ` Eli Zaretskii
2016-08-19 20:27       ` Óscar Fuentes
2016-08-20 15:49       ` Arash Esbati
2016-08-20 15:58         ` Eli Zaretskii
2016-08-22 10:37           ` Phillip Lord
2016-08-22 14:54             ` Eli Zaretskii
2016-08-23 11:26               ` Phillip Lord
2016-08-23 14:35                 ` Eli Zaretskii
2016-08-23 17:02                   ` Arash Esbati
2016-08-23 17:21                     ` Eli Zaretskii
2016-08-24 10:42                   ` Phillip Lord
2016-08-19 15:03 ` Phillip Lord [this message]
2016-08-19 17:24   ` Arash Esbati

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=877fbc3ion.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=arash.esbati@gmail.com \
    --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.