unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "d.henman" <dhenman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: building advice
Date: Sat, 08 Sep 2007 15:09:12 +0300	[thread overview]
Message-ID: <uvealqryv.fsf@gnu.org> (raw)
In-Reply-To: <20070908195710.2004@blackhawk> (dhenman@gmail.com)

> From: "d.henman" <dhenman@gmail.com>
> Date: Sat, 08 Sep 2007 19:57:10 +0900
> cc: 
> 
> I need some advise on how to test certain fixes and not have to rebuild
> the whole emacs cvs tree all over...   This is very time consuming to 
> try build fixes...
> 
> For example, in my case, I am trying to figure out if some changes I made in the tramp files, enables them to byte compile properly on my system.
> 
> I tried using emacs --batch tramp*.el         [with an existing emacs] and
>              temacs --batch tramp*.el	      [with the partially built emacs]
> 
> I am sure there are various environment variables involved in the process as well.
> For now I just make changes, distclean, and rebuild.  This takes as you all know a long time to find out if I did anything right to at least allow a clean compile.

One way to do it easier is to chdir to the lisp/ directory, and then
type these commands:

     make cvs-update EMACS=../src/emacs

if you are on a Unix-like system, or

     make cvs-update EMACS=../src/oo-spd/i386/emacs.exe

if you are on MS-Windows.

  reply	other threads:[~2007-09-08 12:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-08 10:57 building advice d.henman
2007-09-08 12:09 ` Eli Zaretskii [this message]
2007-09-09  0:13   ` d.henman

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=uvealqryv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dhenman@gmail.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 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).