unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Ruslan Bekenev <furyinbox@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Building Emacs with MinGW 64
Date: Sat, 10 Feb 2018 20:42:54 -0500	[thread overview]
Message-ID: <CAM-tV-9dvq++5ib4DeD=WeUyi2VDTSq_NzCNNNjMJb5RL7Qikg@mail.gmail.com> (raw)
In-Reply-To: <41708f1b-7ba7-cc6d-fc8c-3072ef63f4a5@gmail.com>

On Sat, Feb 10, 2018 at 4:10 PM, Ruslan Bekenev <furyinbox@gmail.com> wrote:

> I also have found some build instructions in the web that use MSYS2 package.
> This is not what I want to use though.

You should look at the instructions that come with Emacs first. There
is nt/INSTALL for building with MSYS and mingw32 (I believe this can
only produce 32 bit binaries). nt/INSTALL.w64 describes building with
MSYS2 and mingw64 (this can produce both 64 bit and 32 bit binaries).

You don't explain exactly why you don't want to use MSYS2. Building
Emacs requires gcc, development libraries+headers and a bourne-shell
(or derivative like GNU bash) with standard Unix command line
utilities. MSYS and MSYS2 provide a simple packaged way of installing
these. The nt/INSTALL instructions explain how to install mingw32
separately from MSYS, but I don't know that you can avoid it entirely.



  reply	other threads:[~2018-02-11  1:42 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 [this message]
2018-02-11  9:39   ` Ruslan Bekenev
2018-02-13  8:02     ` Stephen Leake
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='CAM-tV-9dvq++5ib4DeD=WeUyi2VDTSq_NzCNNNjMJb5RL7Qikg@mail.gmail.com' \
    --to=npostavs@users.sourceforge.net \
    --cc=emacs-devel@gnu.org \
    --cc=furyinbox@gmail.com \
    /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).