From: Arash Esbati <esbati@gmx.de>
To: help-gnu-emacs@gnu.org
Subject: Re: 64 bit official Windows builds
Date: Sun, 10 Jan 2016 22:19:01 +0100 [thread overview]
Message-ID: <n6uhs9$dsa$1@ger.gmane.org> (raw)
In-Reply-To: 6b5d747c-7abb-44fc-8f9a-3d629fb892a8@googlegroups.com
Sam Halliday <sam.halliday@gmail.com> writes:
> It sounds like you know how to do this a lot better than I do.
No, not really. I just managed to build Emacs after a recipe you can
find here:
http://sourceforge.net/p/emacsbinw64/wiki/Build%20guideline%20for%20MSYS2-MinGW-w64%20system/
and now here as well:
http://git.savannah.gnu.org/cgit/emacs.git/tree/nt/INSTALL.W64?h=emacs-25
After the discussion here, I looked closer at how Msys2/MinGW-w64
manages its packages.
http://sourceforge.net/p/msys2/wiki/Contributing%20to%20MSYS2/
https://github.com/Alexpux/MINGW-packages
The optional packages for building Emacs are:
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
and their dependencies are: (`pactree --help')
mingw-w64-bzip2
mingw-w64-cairo
mingw-w64-expat
mingw-w64-fontconfig
mingw-w64-freetype
mingw-w64-gdk-pixbuf2
mingw-w64-gettext
mingw-w64-glib2
mingw-w64-gmp
mingw-w64-harfbuzz
mingw-w64-jasper
mingw-w64-libcroco
mingw-w64-libffi
mingw-w64-libiconv
mingw-w64-lzo2
mingw-w64-pango
mingw-w64-pixman
mingw-w64-xz
mingw-w64-zlib
It is possible to build source archives incl. the patches coming from
Msys2 project with `makepkg-mingw' command. The process is start the
`msys2_shell' and do:
--8<---------------cut here---------------start------------->8---
git clone "https://github.com/Alexpux/MINGW-packages"
cd MINGW-packages/mingw-w64-libtiff
MINGW_INSTALLS=mingw64 makepkg-mingw --nobuild -sL
MINGW_INSTALLS=mingw64 makepkg-mingw --allsource -sLf
--8<---------------cut here---------------end--------------->8---
I tried this and it worked for all the packages except for
`mingw-w64-gettext', `mingw-w64-gmp' and `mingw-w64-gnutls'. I have to
take a closer look. So I think it would be possible to provide source
tarballs for the DLLs.
> 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?
Sources of the compiler? Do you mean gcc? No, I won't go there :-)
> 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.
I'm not familiar with appveyor.
Best, Arash
next prev parent reply other threads:[~2016-01-10 21:19 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
2016-01-10 21:19 ` Arash Esbati [this message]
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='n6uhs9$dsa$1@ger.gmane.org' \
--to=esbati@gmx.de \
--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.