From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Building Emacs on Windows with MinGW+MSYS (was: Emacs pretest 24.0.90) Date: Fri, 14 Oct 2011 00:03:54 +0200 Message-ID: <83pqi01rcl.fsf@gnu.org> References: Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1318543523 11608 80.91.229.12 (13 Oct 2011 22:05:23 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 13 Oct 2011 22:05:23 +0000 (UTC) Cc: lekktu@gmail.com, emacs-devel@gnu.org To: Dani Moncayo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 14 00:05:17 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RETOv-00009y-J3 for ged-emacs-devel@m.gmane.org; Fri, 14 Oct 2011 00:05:17 +0200 Original-Received: from localhost ([::1]:55115 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RETOu-0005A0-NU for ged-emacs-devel@m.gmane.org; Thu, 13 Oct 2011 18:05:16 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:46118) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RETOr-00059v-NC for emacs-devel@gnu.org; Thu, 13 Oct 2011 18:05:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RETOq-0000OM-ME for emacs-devel@gnu.org; Thu, 13 Oct 2011 18:05:13 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:59734) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RETOq-0000O2-EC for emacs-devel@gnu.org; Thu, 13 Oct 2011 18:05:12 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0LT000L00YJ45H00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Fri, 14 Oct 2011 00:03:52 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([84.229.17.178]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LT000LK2YMF4O20@a-mtaout22.012.net.il>; Fri, 14 Oct 2011 00:03:52 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 80.179.55.172 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:145160 Archived-At: > Date: Thu, 13 Oct 2011 23:01:22 +0200 > From: Dani Moncayo > Cc: emacs-devel@gnu.org, Eli Zaretskii > > While reading that file, I've tried something that it suggests: to use > "mingw32-make" as the make tool. To my delight, it worked flawlessly! > > So, it's possible to build Emacs on Windows using _exclusively_ the > utilities provided by MinGW, with its MSYS package included (it > supplies necessary utilities like rm or cp). If you use the MinGW Make, then the only tools you need from MSYS are cp, mv, and rm. It makes no sense to install MSYS for these 3 programs. Just install the GnuWin32 Coreutils, and be done. > Thus, I suggest an update of the file nt/INSTALL. In particular, the > last sentence of this paragraph: > > MSYS sh.exe also appears to cause > various problems, e.g., it is known to cause failures in commands > like "cmd /c FOO" in the Makefiles, because it thinks "/c" is a > Unix-style file name that needs conversion to the Windows format. > If you have MSYS installed, try "make SHELL=cmd.exe" to force the > use of cmd.exe instead of the MSYS sh.exe. > > The solution proposed there doesn't seem to work (at least for me). Probably because you tried it with MSYS Make. That solution will only work with the MinGW Make. > And finally, here is and updated version of my recipe to build Emacs on Windows: Sorry, but I see no need to recommend MSYS just to have 3 programs. MSYS is tricky to install if you already have a native MinGW development environment, because you need to keep them separate (due to incompatible features), but still let MSYS invoke MinGW programs, such as the compiler and the linker. Setting this up is not for a casual user. Downloading a single GnuWin32 package is much simpler.