unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: Building Emacs on Windows with MinGW+MSYS (was: Emacs pretest 24.0.90)
Date: Fri, 14 Oct 2011 10:20:56 +0200	[thread overview]
Message-ID: <83ehygkmqf.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0h0SCiggKm00BHu0ELbSqVbZDGD3Lmkwa6x3wX73NaZuQ@mail.gmail.com>

> Date: Fri, 14 Oct 2011 00:23:43 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: lekktu@gmail.com, emacs-devel@gnu.org
> 
> > If you use the MinGW Make, then the only tools you need from MSYS are
> > cp, mv, and rm.  It makes no sense to install MSYS for these 3
> > programs.  Just install the GnuWin32 Coreutils, and be done.
> 
> In my case, it make sense, because MSYS gives me a useful set of tools
> beyond those three: diff, grep, find, touch, cat, ls and many more.

If you use those outside of Emacs, then this benefit is unrelated to
the issue at hand, which is what should be the best recommended way of
building Emacs on Windows.

If you use them from Emacs, then the same caveats apply about
file-name conversion done by MSYS tools.  The MSYS developers
themselves explicitly tell that these tools are not supposed to be
used for any purpose _except_ running the Posix configure scripts and
the Makefile's produced by those scripts, for the explicit goal of
building MinGW packages.  "Building", not "using".  So beware.

> I found it very handy, not only for building Emacs, but to have a
> "minimal system" for programming.

You are using MSYS out of its intended purpose, so it will bite you
some day.




  parent reply	other threads:[~2011-10-14  8:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 21:01 Building Emacs on Windows with MinGW+MSYS (was: Emacs pretest 24.0.90) Dani Moncayo
2011-10-13 22:03 ` Eli Zaretskii
2011-10-13 22:23   ` Dani Moncayo
2011-10-13 23:37     ` Multi-platform build system (was: Building Emacs on Windows with MinGW+MSYS) Óscar Fuentes
2011-10-14  0:09       ` Multi-platform build system Miles Bader
2011-10-14  0:31         ` Óscar Fuentes
2011-10-14  0:55           ` Miles Bader
2011-10-14  1:27             ` Óscar Fuentes
2011-10-14  0:41       ` Multi-platform build system (was: Building Emacs on Windows with MinGW+MSYS) Dan Nicolaescu
2011-10-14  1:43         ` Multi-platform build system Óscar Fuentes
2011-10-14  6:17           ` Dan Nicolaescu
2011-10-14  1:06       ` Multi-platform build system (was: Building Emacs on Windows with MinGW+MSYS) Juanma Barranquero
2011-10-14  1:18         ` Christoph Scholtes
2011-10-14  1:20           ` Juanma Barranquero
2011-10-14  1:47             ` Multi-platform build system Óscar Fuentes
2011-10-14  1:33         ` Óscar Fuentes
2011-10-14  1:43           ` Juanma Barranquero
2011-10-14  2:52             ` Óscar Fuentes
2011-10-14  3:17               ` Juanma Barranquero
2011-10-14  1:57         ` Miles Bader
2011-10-14  2:05           ` Juanma Barranquero
2011-10-14  2:28             ` Miles Bader
2011-10-14  2:31               ` Juanma Barranquero
2011-10-14  5:01           ` Stephen J. Turnbull
2011-10-14 13:18       ` Stefan Monnier
2011-10-14  8:20     ` Eli Zaretskii [this message]
2011-10-13 23:09   ` Building Emacs on Windows with MinGW+MSYS Miles Bader
2011-10-14  8:16     ` Eli Zaretskii

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=83ehygkmqf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dmoncayo@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@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).