unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Subject: Re: NT Emacs make problem..
Date: 10 Jun 2002 00:44:05 +0200	[thread overview]
Message-ID: <5xr8jg9ioa.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <vafelfgqwps.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Richard Stallman <rms@gnu.org> writes:
> 
> > What else do people need to know [to build Emacs from CVS]?
>

I work on other project where I need to use CVSREAD=y

This means that I have to checkout (not update)

        cvs co ...
        chmod -R u+w .
        ./configure
        make bootstrap

However, if you build in a different directory (the details are in INSTALL),
you can avoid "polluting" the checked out sources with the build.

> And then, people might be interested in a fast method that does as
> little as possible after a CVS update.  I think that it is possible
> to be even faster than "make all"?

I typically use the following to update and compile:

        cvs up
        (cd lisp; make recompile)
        make

PS:  I suggested to create an INTRO_CVS file a while back which should
contain just this kind of information; maybe you can grep through the
emacs-devel archives to see what was suggested back then.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2002-06-09 22:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.SUN.3.91.1020605143252.7779A-100000@is>
     [not found] ` <ap3bsapg081.fsf@student1.physics.umd.edu>
     [not found]   ` <9735-Wed05Jun2002210858+0300-eliz@is.elta.co.il>
2002-06-07  0:44     ` NT Emacs make problem Richard Stallman
2002-06-07  1:11       ` Thien-Thi Nguyen
2002-06-08 19:15         ` Richard Stallman
2002-06-08 20:20           ` Thien-Thi Nguyen
2002-06-10 10:15             ` Richard Stallman
2002-06-10 10:39               ` Thien-Thi Nguyen
2002-06-11 17:16                 ` D. Goel
2002-06-07 13:37       ` Eli Zaretskii
2002-06-07 14:09         ` D. Goel
2002-06-07 15:07           ` Simon Josefsson
2002-06-07 16:47             ` D. Goel
2002-06-08 19:15           ` Richard Stallman
2002-06-09  3:11             ` D. Goel
2002-06-10 10:14               ` Richard Stallman
2002-06-10 11:34                 ` Kai Großjohann
2002-06-11 17:11                 ` D. Goel
2002-06-11 19:29                   ` Kai Großjohann
2002-06-12 12:14                     ` Richard Stallman
2002-06-12 13:13                       ` Stefan Monnier
2002-06-13  4:55                         ` Eli Zaretskii
2002-06-13 21:46                         ` Richard Stallman
2002-06-12 13:37                       ` Kai Großjohann
2002-06-13 21:47                         ` Richard Stallman
2002-06-12 14:33                       ` Andreas Schwab
2002-06-13 14:36                       ` D. Goel
2002-06-12  2:34                   ` Richard Stallman
2002-06-12  4:48                     ` Eli Zaretskii
2002-06-12 12:42                       ` Richard Stallman
2002-06-12  8:28                     ` Simon Josefsson
2002-06-09 15:48             ` Kai Großjohann
2002-06-09 22:44               ` Kim F. Storm [this message]
2002-06-10 23:44               ` Richard Stallman

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=5xr8jg9ioa.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    /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).