[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: minor windoze build bug

From: Eli Zaretskii
Subject: Re: minor windoze build bug
Date: Sat, 19 Nov 2005 11:25:41 +0200

[Please keep address@hidden on the CC list.]

> Date: Sat, 19 Nov 2005 00:54:52 -0800 (PST)
> From: Martins Krikis <address@hidden>
> Cc: address@hidden
> > Others succeeded building Emacs with MSVC without moving the tree.  I
> > suspect that your problem happens because of some bad interaction
> > between NMAKE and that ``bit of Cygwin''.  I suggest to make sure you
> > use combinations of tools which are described in nt/INSTALL as
> > successful.
> I tried, but didn't get very far. nmake was complaining about
> lack of "sh.exe", "cp", etc., don't remember anymore.

May I suggest that you post here a complete transcript of your build
attempts?  As nt/INSTALL tells you, cp.exe, rm.exe, and mv.exe are
required for the build, but sh.exe is not.  nt/configure.bat will tell
you what is needed and what is merely checked and marked as

> Perhaps I'm too clueless about Windoze tools but I certainly
> couldn't build it without adding cygwin paths to the Windoze
> build-window.

There are non-Cygwin ports of cp, rm, and mv.  One place to look is on
the GnuWin32 site.

> Ideally, though, I'd love to be able to build it using pure Cygwin
> tools and don't see much need for mingw (other than what's in Cygwin
> anyway?).

If you want a Cygwin build of Emacs, you will have to use the CVS
sources.  Only the current development version supports a Cygwin
build out of the box.

Alternatively, I'm told that there's a prebuilt binary in the Cygwin
archives, which you could use.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]