From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs build on Windows: Prerequisites
Date: Wed, 28 Feb 2007 22:25:03 +0200 [thread overview]
Message-ID: <uirdm6nds.fsf@gnu.org> (raw)
In-Reply-To: <87r6sai5m5.fsf@uwakimon.sk.tsukuba.ac.jp> (stephen@xemacs.org)
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Date: Thu, 01 Mar 2007 01:55:46 +0900
> Cc: Emacs Devel <emacs-devel@gnu.org>
>
> > Why should Emacs build on windows need those tools? Why can't it use
> > the windows equivalents?
>
> Because they're not equivalent. They are by and large much less
> powerful, with idiosyncratic syntax that often does not mix well with
> scripts and idiosyncratic semantics such as rather low limits on
> number of command line arguments, causing mysterious build failures.
That was so in the past, but Windows versions since W2K on don't have
these limitations, and the equivalent commands are as powerful as the
Posix ones. However, we still support the older versions of Windows.
next prev parent reply other threads:[~2007-02-28 20:25 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
2007-02-28 16:55 ` Stephen J. Turnbull
2007-02-28 20:25 ` Eli Zaretskii [this message]
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
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=uirdm6nds.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).