all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs build on Windows: Prerequisites
Date: Thu, 01 Mar 2007 06:17:43 +0200	[thread overview]
Message-ID: <u4pp57g2g.fsf@gnu.org> (raw)
In-Reply-To: <45E5FCB5.5050104@gnu.org> (message from Jason Rumney on Wed, 28 Feb 2007 22:05:41 +0000)

> Date: Wed, 28 Feb 2007 22:05:41 +0000
> From: Jason Rumney <jasonr@gnu.org>
> Cc: Emacs Devel <emacs-devel@gnu.org>
> 
> There are a couple of paragraphs of commentary in nt/gmake.defs about 
> why past maintainers chose to require cp and rm to build Emacs rather 
> than use the Windows native del and copy commands.

Some of those reasons are also a thing of the past.  For example,
latest versions of GNU Make do support setting SHELL to cmd.exe.  But
backslashes in file names is still sometimes an issue, even though
quoting file names solves that in some cases.

  parent reply	other threads:[~2007-03-01  4:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 12:58 Emacs build on Windows: Prerequisites dhruva
2007-02-28 13:11 ` David Kastrup
2007-02-28 13:31   ` dhruva
2007-02-28 22:05     ` Jason Rumney
2007-03-01  4:17       ` dhruva
2007-03-01 10:44         ` Lennart Borgman (gmail)
2007-03-02 14:28         ` Vinicius Jose Latorre
2007-03-02 14:57           ` Lennart Borgman (gmail)
2007-03-02 15:20             ` Vinicius Jose Latorre
2007-03-02 15:33               ` Lennart Borgman (gmail)
2007-03-02 19:41                 ` Vinicius Jose Latorre
2007-03-02 20:10                   ` Lennart Borgman (gmail)
2007-03-02 20:51                     ` Vinicius Jose Latorre
2007-03-03 10:33                     ` Eli Zaretskii
2007-03-03 13:54                       ` Lennart Borgman (gmail)
2007-03-01  4:17       ` Eli Zaretskii [this message]
2007-02-28 16:55 ` Stephen J. Turnbull
2007-02-28 20:25   ` Eli Zaretskii
2007-02-28 20:18 ` 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=u4pp57g2g.fsf@gnu.org \
    --to=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.