all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christoph Scholtes <cschol2112@googlemail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs build times on Windows
Date: Sat, 21 Apr 2012 16:52:40 +0300	[thread overview]
Message-ID: <83r4vhgpjr.fsf@gnu.org> (raw)
In-Reply-To: <4F92A296.3000604@gmail.com>

> Date: Sat, 21 Apr 2012 06:05:42 -0600
> From: Christoph Scholtes <cschol2112@googlemail.com>
> CC: emacs-devel@gnu.org
> 
> > On my i7 desktop (4 hyper-threaded cores), it takes 9 minutes, if I
> > use the -j10 switch to Make.  I suggest that you try -j6 in your
> > builds (if you use anything older than the current CVS of GNU Make,
> > you will also have to use the XMFLAGS="-j6" kludge as well, see
> > nt/INSTALL).  A parallel build should be faster.
> 
> Thanks. Does this work with mingw32-make also or do I have to use Cygwin 
> (or MSYS?) to obtain gmake?

Parallel builds are supported by the native Windows build of GNU Make
since v3.81.  So if you have mingw32-make v3.81 or 3.82, you should be
all set for parallelism.

> I tried building with mingw32-make -j2 but it did not result in any 
> significant speedup.

Like I said: you need to say "mingw32-make -j2 XMFLAGS=-j2" for this
to work.

The issue here is that the native Windows build of Make does not yet
support the "job server" method of parallel execution, which causes
the number of jobs in each sub-Make be reset to 1.  The XMFLAGS=-j2
kludge works around that by forcing the sub-Make's to use an explicit
"-jN" switch.

(The current CVS code of Make includes a job server implementation for
Windows, so the next release of Make will free us from this kludge.)

> > IOW, we use a shell-level loop to compile the files one by one.
> >
> > So if you are looking for the place to significantly speed up the
> > bootstrap, the first place to look is to make the byte compilation use
> > a similar setup to what you see in lisp/Makefile.in.
> 
> I see. I will look into that. Thanks.

Thanks in advance.



      reply	other threads:[~2012-04-21 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21  3:50 Emacs build times on Windows Christoph Scholtes
2012-04-21  7:29 ` Eli Zaretskii
2012-04-21 12:05   ` Christoph Scholtes
2012-04-21 13:52     ` Eli Zaretskii [this message]

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=83r4vhgpjr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cschol2112@googlemail.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.