From: Andy Moreton <andrewjmoreton@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Make check in trunk
Date: Tue, 02 Sep 2014 18:52:30 +0100 [thread overview]
Message-ID: <vz1iol5ucyp.fsf@gmail.com> (raw)
In-Reply-To: 83d2bef0wk.fsf@gnu.org
On Tue 02 Sep 2014, Eli Zaretskii wrote:
>> From: Óscar Fuentes <ofv@wanadoo.es>
>> Date: Tue, 02 Sep 2014 17:59:53 +0200
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > What would be the reasons for anyone to switch from MSYS to MSYS2?
>>
>> MSYS2 has lots of up-to-date packages which are straightforward to
>> install. Starting from zero, you can setup the complete requirements for
>> building Emacs as fast as your Internet connection allows.
>
> OK, but I asked about switching from MSYS, which presumes that such an
> environment based on MSYS is already set up. Why would one want to
> switch?
I switched over last week, in order to start using the Mingw64 compiler
in a painless way. The MSYS2 environment can be setup in very little
time, and a GUI installer is available to get started.
The package manager (pacman, ported from Arch Linux) handles installing
the toolchains and their dependencies. The package archives include all
of the optional dependencies for emacs on Windows (image libaries, XML,
GnuTLS etc).
HTH,
AndyM
next prev parent reply other threads:[~2014-09-02 17:52 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vz1iol5ucyp.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).