all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: Make check in trunk
Date: Thu, 04 Sep 2014 14:09:57 -0500	[thread overview]
Message-ID: <85ha0n42yi.fsf@stephe-leake.org> (raw)
In-Reply-To: <86bnqxobb5.fsf@gmail.com> (Andy Moreton's message of "Wed, 03 Sep 2014 00:24:46 +0100")

Andy Moreton <andrewjmoreton@gmail.com> writes:

> On Tue 02 Sep 2014, Eli Zaretskii wrote:
>
>>> From: Andy Moreton <andrewjmoreton@gmail.com>
>>> 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?

I was under the impression that it could not. It would certainly require
compiling the 64 bit gcc toolchain from scratch; it is _far_ easier to
install MSYS2.

>> 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.

+2 :)

-- 
-- Stephe



  parent reply	other threads:[~2014-09-04 19:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06 20:51 Make check in trunk Fabrice Popineau
2014-09-02  6:01 ` Fabrice Popineau
2014-09-02 14:47   ` Eli Zaretskii
2014-09-02 15:59     ` Óscar Fuentes
2014-09-02 16:22       ` Eli Zaretskii
2014-09-02 16:34         ` Óscar Fuentes
2014-09-02 18:00           ` Eli Zaretskii
2014-09-02 20:00             ` Óscar Fuentes
2014-09-02 17:52         ` Andy Moreton
2014-09-02 18:08           ` Eli Zaretskii
2014-09-02 23:24             ` Andy Moreton
2014-09-03 17:02               ` Eli Zaretskii
2014-09-04 19:09               ` Stephen Leake [this message]
2014-09-05  6:54                 ` Eli Zaretskii
2014-09-02 23:20     ` Fabrice Popineau

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85ha0n42yi.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.