From: Sam Halliday <sam.halliday@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: 64 bit official Windows builds
Date: Sat, 9 Jan 2016 05:04:49 -0800 (PST) [thread overview]
Message-ID: <6b5d747c-7abb-44fc-8f9a-3d629fb892a8@googlegroups.com> (raw)
In-Reply-To: <mailman.1913.1452206888.843.help-gnu-emacs@gnu.org>
Arash,
It sounds like you know how to do this a lot better than I do.
Is there any chance you could package this up so that everybody can get your 64 bit builds of Emacs for Windows from the FSF site? If the sources are listed already, maybe you could just create a tarball containing all the sources of the compiler and required libraries?
It would be really good from an automation point of view if you could write a little recipe (maybe an appveyor script?) that could be triggered when new versions of emacs (or the compiler) are released.
Best regards,
Sam
On Thursday, 7 January 2016 22:48:10 UTC, Arash Esbati wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Óscar Fuentes <ofv@wanadoo.es>
> >> Date: Fri, 25 Dec 2015 14:35:46 +0100
> >>
> >> IIRC the problematic part is to create and distribute a source tarball
> >> with all the libraries included on the binary package (graphic
> >> libraries, SSL, etc). This was discussed on the past and can't recall
> >> the outcome.
> >
> > It's up to the person who volunteers for the job. It's quite okay to
> > upload only the Emacs binary that was compiled with support for the
> > optional libraries, and expect the end users to download and itsall
> > the DLLs separately. It is also okay to upload the DLLs as part of
> > the binary distro, but then the corresponding sources should be on the
> > same site.
>
> I think that providing bare Emacs binaries without the corresponding
> dll's is not really user friendly. I build Emacs on my Win 64bit
> machine with Msys2/MinGW-w64 and it would be pain if I had to collect all
> dll's myself somehow. OTOH, collecting and providing all the sources
> along with the dll's is also not fun. Can there be a compromise? For
> Msys2/MinGW-w64, all PKGBUILD files contain references the sources, e.g.:
>
> https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-libidn/PKGBUILD
>
> So one could say: Consult the PKGBUILD files for the sources
> (incl. dependencies) for
>
> - mingw-w64-libtiff
> - mingw-w64-giflib
> - mingw-w64-libpng
> - mingw-w64-libjpeg-turbo
> - mingw-w64-librsvg
> - mingw-w64-libxml2
> - mingw-w64-gnutls
> - mingw-w64-xpm-nox
>
> Best, Arash
next prev parent reply other threads:[~2016-01-09 13:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 23:01 64 bit official Windows builds Sam Halliday
2015-12-25 7:35 ` Eli Zaretskii
2015-12-25 13:35 ` Óscar Fuentes
2015-12-25 14:21 ` Eli Zaretskii
2015-12-25 15:32 ` Random832
2015-12-25 15:52 ` Eli Zaretskii
2016-01-07 22:47 ` Arash Esbati
2016-01-08 9:12 ` Eli Zaretskii
2016-01-08 21:42 ` Arash Esbati
2016-01-09 6:58 ` Eli Zaretskii
[not found] ` <mailman.1936.1452244338.843.help-gnu-emacs@gnu.org>
2016-01-08 10:44 ` Sam Halliday
2016-01-08 11:09 ` Eli Zaretskii
[not found] ` <mailman.1913.1452206888.843.help-gnu-emacs@gnu.org>
2016-01-09 13:04 ` Sam Halliday [this message]
2016-01-10 21:19 ` Arash Esbati
2016-02-11 21:21 ` Nicolas Petton
2016-02-11 21:35 ` Kaushal Modi
2016-02-11 21:53 ` John Mastro
[not found] ` <mailman.556.1451028922.843.help-gnu-emacs@gnu.org>
2016-01-07 22:38 ` Sam Halliday
2016-01-07 23:15 ` Rasmus
2016-01-08 9:05 ` Eli Zaretskii
2016-02-08 17:44 ` moocow062
2016-02-08 18:06 ` Eli Zaretskii
2016-02-08 18:29 ` Óscar Fuentes
2016-02-08 19:10 ` Eli Zaretskii
2016-02-11 13:58 ` Stefan Monnier
2016-02-11 20:50 ` Eli Zaretskii
2016-02-11 22:16 ` Óscar Fuentes
2016-02-12 6:55 ` Eli Zaretskii
2016-02-12 7:16 ` Óscar Fuentes
2016-02-12 7:48 ` Eli Zaretskii
2016-02-12 8:16 ` Óscar Fuentes
2016-02-12 8:51 ` Eli Zaretskii
2016-02-08 22:13 ` djc
2016-02-08 22:51 ` Óscar Fuentes
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=6b5d747c-7abb-44fc-8f9a-3d629fb892a8@googlegroups.com \
--to=sam.halliday@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.