unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Sam Halliday <sam.halliday@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: 64 bit official Windows builds
Date: Thu, 7 Jan 2016 14:38:38 -0800 (PST)	[thread overview]
Message-ID: <93454cca-ce83-4763-85d6-7d1f3f12931c@googlegroups.com> (raw)
In-Reply-To: <mailman.556.1451028922.843.help-gnu-emacs@gnu.org>

On Friday, 25 December 2015 07:35:25 UTC, Eli Zaretskii  wrote:
> > Date: Thu, 24 Dec 2015 15:01:53 -0800 (PST)
> > From: Sam Halliday <sam.halliday@gmail.com>
> > 
> > Are there any plans for GNU to create official 64 bit builds of
> > Emacs releases?
> 
> this simply needs a volunteer who'd be prepared to
> produce the binaries, package them in a compressed archive, set up
> uploading rights to the GNU servers, and upload the stuff whenever a
> new release is out.

I'm happy (this is a relative term when Windoze is involved) to create the builds. I have a virtual Windows image that I use for testing. Can somebody please point me at the exact instructions that I need to follow? Most of my computing experience is with GNU/Linux, so knowing exactly how to set up the build environment would be useful, although I can fumble my way to getting the GNU chain installed, I'm sure.


Incidentally, http://www.appveyor.com/ can be used in continuous integration for testing on Windows. I use it in my free software projects and its a real time saver. If GNU Emacs was hosted on github it would be possible to trigger a Windows test on every push to master (this might be possible as a mirror). I use a combination of appveyor and a self-hosted https://github.com/drone/drone/ to test, build and deploy our continual delivery releases for all major platforms.

So, ideally, I'd like to get the GNU Emacs windows builds running off an appveyor script so it should work with the click of a button.



  parent reply	other threads:[~2016-01-07 22:38 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
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 [this message]
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

  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=93454cca-ce83-4763-85d6-7d1f3f12931c@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.
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).