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: Make check in trunk Date: Wed, 03 Sep 2014 20:02:33 +0300 Message-ID: <8338c8iqmu.fsf@gnu.org> References: <83ppfef59r.fsf@gnu.org> <87wq9m813a.fsf@wanadoo.es> <83d2bef0wk.fsf@gnu.org> <837g1lgajz.fsf@gnu.org> <86bnqxobb5.fsf@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1409763773 13742 80.91.229.3 (3 Sep 2014 17:02:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 3 Sep 2014 17:02:53 +0000 (UTC) Cc: emacs-devel@gnu.org To: Andy Moreton Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 03 19:02:46 2014 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 1XPDxC-0002DP-KS for ged-emacs-devel@m.gmane.org; Wed, 03 Sep 2014 19:02:42 +0200 Original-Received: from localhost ([::1]:46690 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XPDxB-0008K7-Vb for ged-emacs-devel@m.gmane.org; Wed, 03 Sep 2014 13:02:41 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53391) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XPDx2-0008K1-RR for emacs-devel@gnu.org; Wed, 03 Sep 2014 13:02:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XPDwv-0003St-CO for emacs-devel@gnu.org; Wed, 03 Sep 2014 13:02:32 -0400 Original-Received: from mtaout25.012.net.il ([80.179.55.181]:37188) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XPDwv-0003SY-59 for emacs-devel@gnu.org; Wed, 03 Sep 2014 13:02:25 -0400 Original-Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0NBC00D0046VE000@mtaout25.012.net.il> for emacs-devel@gnu.org; Wed, 03 Sep 2014 19:56:58 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NBC005SS4EXJJ80@mtaout25.012.net.il>; Wed, 03 Sep 2014 19:56:57 +0300 (IDT) In-reply-to: <86bnqxobb5.fsf@gmail.com> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.181 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:173992 Archived-At: > From: Andy Moreton > Date: Wed, 03 Sep 2014 00:24:46 +0100 > > On Tue 02 Sep 2014, Eli Zaretskii wrote: > > >> From: Andy Moreton > >> Date: Tue, 02 Sep 2014 18:52:30 +0100 > >> > >> I switched over last week, in order to start using the Mingw64 compiler > >> in a painless way. > > > > Are you saying that MSYS cannot run MinGW64? > > > > If not, what do you mean by "painless"? What kind of pain did you > > experience before? > > The mingw project is rudderless, and up until only a couple of weeks ago > had been advertising a broken compiler and runtime as its current > release for months. > > Setting up a working MSYS/mingw build environment with a consistent set > of libraries for optional emacs features (images, XML, etc.) is a > pain. The mingw/MSYS world does not have any package management worth > the name. > > MSYS2 is simply a more recent fork from Cygwin than MSYS. The project > has 32bit and 64bit MSYS2 environments, and packages including mingw and mingw64 > (32 and 64bit) toolchains and libs. It is far easier to install a full > consistent set of dependencies with a working package manager. > > I want a simple way to get a full featured up to date emacs build, and > then use it for productive work. I do not want to spend my time tracking > down the right combination of tools and libraries (or have to build all > of them myself). At the moment, MSYS2 with a mingw64 toolchain fits that > requirement far better than mingw/MSYS. Thanks.