unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org, jasonr@gnu.org
Subject: Re: [Emacs-diffs] Changes to emacs/nt/INSTALL,v
Date: Fri, 11 Apr 2008 13:22:48 +0300	[thread overview]
Message-ID: <umyo0adxj.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0804110213q58314d8ana76dc839348abded@mail.gmail.com>

> Date: Fri, 11 Apr 2008 11:13:05 +0200
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: jasonr@gnu.org, emacs-devel@gnu.org
> 
> >  cvs-update was introduced as a very useful shortcut, which takes half
> >  a minute, if only a few Lisp files were modified
> 
> Hm. I would've said that the whole point of cvs-update is to be more
> correct than recompile; else, why not simply use recompile, which is
> faster?

Because without the other prerequisites of cvs-update, especially
autoloads, you will have a buggy Emacs.

> > rather than one and
> > a half hour taken by bootstrapping.
> 
> Just out of curiosity: in what kind of hardware? On a 3GHz Pentium 4,
> it takes less than half an hour for me, from `make maintainer-clean'
> to installation (though I cut some time by always doing an in-place
> installation). That with MinGW's gcc; when I used Visual C it was even
> faster.

It's the same hardware, so maybe half an hour is so long for me that I
took it for three times that ;-)  I don't really remember how long it
was exactly, but it seemed forever.

> I'm more interested in the question of whether nt makefile's
> recompile should call lisp makefile's cvs-update, or perhaps recompile
> + updates.

I never do a "make recompile" from the nt subdirectory.




  reply	other threads:[~2008-04-11 10:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Jjscj-0002sL-1T@cvs.savannah.gnu.org>
2008-04-10  9:36 ` [Emacs-diffs] Changes to emacs/nt/INSTALL,v Juanma Barranquero
2008-04-10  9:50   ` Jason Rumney
2008-04-10 17:53     ` Recommended build procedure [was Re: [Emacs-diffs] Changes to emacs/nt/INSTALL, v] Glenn Morris
2008-04-10 19:52   ` [Emacs-diffs] Changes to emacs/nt/INSTALL,v Eli Zaretskii
2008-04-10 20:21     ` Jason Rumney
2008-04-10 22:24     ` Juanma Barranquero
2008-04-11  8:43       ` Eli Zaretskii
2008-04-11  9:13         ` Juanma Barranquero
2008-04-11 10:22           ` Eli Zaretskii [this message]
2008-04-11 10:46             ` Juanma Barranquero
2008-04-11 14:40               ` Eli Zaretskii

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=umyo0adxj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=lekktu@gmail.com \
    /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).