unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Angelo Graziosi <angelo.g0@libero.it>
Cc: emacs-devel@gnu.org
Subject: Re: windows build help
Date: Sat, 14 Oct 2017 12:16:10 +0100	[thread overview]
Message-ID: <87lgke7zet.fsf@russet.org.uk> (raw)
In-Reply-To: <35124014.860629.1507968993303@mail.libero.it> (Angelo Graziosi's message of "Sat, 14 Oct 2017 10:16:33 +0200 (CEST)")

Angelo Graziosi <angelo.g0@libero.it> writes:

> Phillip Lord wrote:
>
>> But I do the x86_64 building using the MINGW64 shell
>> (i.e. C:\msys64\mingw64.exe) and the i686 using MINGW32
>
> in my script I added this:
>
>   MSYSTEM="MINGW64"
>   PATH="/mingw64/bin:$PATH"
>
> Also this should work:
>
>   MSYSTEM=MINGW64 PATH="/mingw64/bin:$PATH" ~/emacs-w64-build.sh
>
>> the entire build takes about an hour or two
>
> On which machine? Here (an Athlon X2, 10 years old), with 'make -j3',
> the build [1] takes about 35-40 minutes [2].

The majority of the time is the elc compilation. So, the first build
takes a long time, second much (much) less.

There is also quite a lot of baggage on top of this. After the zip files
have been build, I have to unzip them, so I check they run cleanly. This
takes around 5 minutes per zip. For Emacs-26, I'm making four zips. Then
the uploads. I normally do it over two days.

Phil




  reply	other threads:[~2017-10-14 11:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-14  8:16 windows build help Angelo Graziosi
2017-10-14 11:16 ` Phillip Lord [this message]
     [not found] <84o9pyim1a.fsf@AigleRoyal>
     [not found] ` <v9tvzoyonq.fsf@fencepost.gnu.org>
     [not found]   ` <c26025cd-ccaa-70e1-94d4-003b7632bd19@gmail.com>
     [not found]     ` <bypoab3jsz.fsf@fencepost.gnu.org>
     [not found]       ` <vz1shf7dl4u.fsf@gmail.com>
     [not found]         ` <83r2up976t.fsf@gnu.org>
     [not found]           ` <CAM-tV-8BAheHD+gDjJ1N+jPYqg8a4MLKK7NEQH=KBWkwjGujuQ@mail.gmail.com>
     [not found]             ` <83bmlblfca.fsf@gnu.org>
     [not found]               ` <vz14lr373si.fsf@gmail.com>
2017-10-13 18:52                 ` Phillip Lord
2017-10-13 19:36                   ` Óscar Fuentes
2017-10-13 19:38                   ` Stephen Leake
2017-10-14 11:07                     ` Phillip Lord
2017-10-14 15:15                       ` Stephen Leake
2017-10-14 15:26                         ` Phillip Lord
2017-10-14 15:31                         ` Eli Zaretskii
2017-10-14 23:04                         ` Paul Eggert
2017-10-16  1:53                           ` Richard Stallman
2017-10-16  6:49                             ` Paul Eggert
2017-10-16 13:54                               ` Stefan Monnier
2017-10-13 19:47                   ` Noam Postavsky
2017-10-14 11:09                     ` Phillip Lord

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=87lgke7zet.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=angelo.g0@libero.it \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).