From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Some comments on the MSYS-based build Date: Mon, 03 Jun 2013 20:01:59 +0200 Message-ID: <87hahfysx4.fsf@wanadoo.es> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1370282545 6600 80.91.229.3 (3 Jun 2013 18:02:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 3 Jun 2013 18:02:25 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 03 20:02:24 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UjZ5M-0006si-CI for ged-emacs-devel@m.gmane.org; Mon, 03 Jun 2013 20:02:24 +0200 Original-Received: from localhost ([::1]:59508 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjZ5M-0003FR-1j for ged-emacs-devel@m.gmane.org; Mon, 03 Jun 2013 14:02:24 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44099) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjZ5D-0003FD-OO for emacs-devel@gnu.org; Mon, 03 Jun 2013 14:02:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UjZ59-0004yT-2q for emacs-devel@gnu.org; Mon, 03 Jun 2013 14:02:15 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:57338) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjZ58-0004yN-Sv for emacs-devel@gnu.org; Mon, 03 Jun 2013 14:02:11 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UjZ57-0006m9-WF for emacs-devel@gnu.org; Mon, 03 Jun 2013 20:02:10 +0200 Original-Received: from 237.red-83-43-53.dynamicip.rima-tde.net ([83.43.53.237]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 03 Jun 2013 20:02:09 +0200 Original-Received: from ofv by 237.red-83-43-53.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 03 Jun 2013 20:02:09 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 45 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 237.red-83-43-53.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:mNhNJ3BxtmEZrzz3FtuR0vc74eI= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:160052 Archived-At: /nt/INSTALL.MSYS says "A nice GUI installer, called mingw-get," mingw-get has no GUI yet. It is a planned feature. However, mingw-get-inst (confusing, uh?) is a GUI front-end that invokes mingw-get for MinGW/MSYS installation. It onlyl supports the most essential packages, though. The URL for mingw-get-inst is: http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/ /nt/INSTALL.MSYS says that mingw-developer-toolkit and msys-automake should be installed. The mingw-get XML file for mingw-developer-toolkit says that it includes mingw-automake and the XML file for msys-automake says: This msys port of automake has been modified specifically for the MSYS System Builder (msys-dvlpr) environment; that is, it is intended to be used only when producing binary packages for the MSYS subsystem. If you intend to produce executables for the native "mingw32" subsystem (that is, applications that should work on Microsoft Windows installations without the MSYS dll), then you should install the mingw32-automake-*, and/or the mingw32-automake1.NN-* packages instead. so it seems that msys-automake is unnecesary. MSYS has its own top-level configure script (/nt/msysconfig.sh) Shall we expect from it the same features than from /confgiure.sh? (modulo OS differences) For instance, /INSTALL mentions `GZIP_PROG' is the name of the executable that compresses installed info, manual, and .el files. It defaults to gzip. Setting it to the empty string suppresses compression. and my build script has export GZIP_PROG="" # Do not compress .elc files if ! ../emacs/nt/msysconfig.sh --prefix $einstall ; then exit 12 fi but the build compresses the .el files.