From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Jason Rumney" <jasonr@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] Changes to emacs/nt/INSTALL,v
Date: Thu, 10 Apr 2008 11:36:58 +0200 [thread overview]
Message-ID: <f7ccd24b0804100236g43d0e6am5a448989171b1ff1@mail.gmail.com> (raw)
In-Reply-To: <E1Jjscj-0002sL-1T@cvs.savannah.gnu.org>
On Thu, Apr 10, 2008 at 10:59 AM, Jason Rumney <jasonr@gnu.org> wrote:
> + make recompile
> + Recompiles any changed lisp files after a cvs update. This saves
> + doing a full bootstrap after every update. If this or a subsequent
> + make fail, you probably need to perform a full bootstrap, though
> + running this target multiple times may eventually sort out the
> + interdependencies.
Currently, the `recompile' target of nt/makefile.w32-in runs the
`recompile' target of lisp/makefile. It would be perhaps more useful
to run the `cvs-update' target introduced by Eli:
# This is useful after "cvs up".
cvs-update: recompile autoloads finder-data custom-deps
BTW, what is the `updates' target of lisp/Makefile.in (and
makefile.w32-in) used for?
updates: update-subdirs autoloads finder-data custom-deps
Perhaps `cvs-update' should just be:
cvs-update: recompile updates
as, after a cvs up, it makes sense to do update-subdirs.
Juanma
next parent reply other threads:[~2008-04-10 9:36 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 ` Juanma Barranquero [this message]
2008-04-10 9:50 ` [Emacs-diffs] Changes to emacs/nt/INSTALL,v 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b0804100236g43d0e6am5a448989171b1ff1@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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.