From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Building Emacs with MinGW 64
Date: Tue, 13 Feb 2018 02:02:57 -0600 [thread overview]
Message-ID: <86eflpnwpa.fsf@stephe-leake.org> (raw)
In-Reply-To: <30b7a1f1-62e9-5b47-3756-5b7d6da7aca8@gmail.com> (Ruslan Bekenev's message of "Sun, 11 Feb 2018 12:39:57 +0300")
Ruslan Bekenev <furyinbox@gmail.com> writes:
> Thank you for the answer, Noam.
>
>> You should look at the instructions that come with Emacs first.
> Sure I did. But thank to your message I noticed NT folder which I've
> missed.
>
>> You don't explain exactly why you don't want to use MSYS2.
> I'm just afraid it's another toolchain I have to keep on my system and
> I have to make sure it's not conflicting with other. As far as I got
> MinGW has GCC and Make and some other tools like sed, grep, sh, etc.
> So I didn't get the point of using MSYS2.
>
> But anyway, thank you again for your answer. I'll try to look deeper
> to the MSYS2. I guess I've just misunderstood the purpose of msys.
You are not alone; the msys and mingw websites do a terrible job of
explaining this.
Roughly, msys is for running bash scripts like configure, while mingw is
the runtime libraries.
--
-- Stephe
next prev parent reply other threads:[~2018-02-13 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 21:10 Building Emacs with MinGW 64 Ruslan Bekenev
2018-02-11 1:42 ` Noam Postavsky
2018-02-11 9:39 ` Ruslan Bekenev
2018-02-13 8:02 ` Stephen Leake [this message]
2018-02-13 15:47 ` Eli Zaretskii
[not found] ` <87tvuh2kl3.fsf@russet.org.uk>
2018-02-16 12:19 ` Phillip Lord
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=86eflpnwpa.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 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).