From: Eli Zaretskii <eliz@gnu.org>
To: Ilya Zakharevich <ilya@math.berkeley.edu>
Cc: ofv@wanadoo.es, 19989@debbugs.gnu.org
Subject: bug#19989: 25.0.50; Build instructions on Windows
Date: Sat, 07 Mar 2015 11:19:39 +0200 [thread overview]
Message-ID: <83d24lmafo.fsf@gnu.org> (raw)
In-Reply-To: <20150307014720.GD18273@math.berkeley.edu>
> Date: Fri, 6 Mar 2015 17:47:21 -0800
> From: Ilya Zakharevich <ilya@math.berkeley.edu>
> Cc: Eli Zaretskii <eliz@gnu.org>, martin rudalics <rudalics@gmx.at>,
> 19989@debbugs.gnu.org
>
> On Fri, Mar 06, 2015 at 03:14:29PM +0100, Óscar Fuentes wrote:
> > Another option is to recommend MSYS2 for those interested on building
> > Emacs on Windows. It is a straightforward process.
>
> Is there any technical reason for not going the way of
> CC=i686-pc-mingw32-gcc
> LINK=i686-pc-mingw32-gcc
> ./configure
> make
> in cygwin’s bash?
I don't think anyone tried that.
One problem you might bump into is that building Emacs requires to
actually run Emacs you've built, and also lib-src/make-docfile, which
are not Cygwin programs. If the Cygwin shell invokes them with
Cygwin-style absolute file names, these programs might fail, claiming
that files don't exist. That's exactly the problem that MSYS attempts
to solve; it is otherwise just a fork of Cygwin.
next prev parent reply other threads:[~2015-03-07 9:19 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 16:34 bug#19989: 25.0.50; Build instructions on Windows Ilya Zakharevich
2015-03-03 17:00 ` Eli Zaretskii
2015-03-03 17:21 ` Eli Zaretskii
2015-03-03 20:30 ` Ilya Zakharevich
2015-03-04 3:42 ` Eli Zaretskii
2015-03-05 21:18 ` Ilya Zakharevich
2015-03-06 8:29 ` Eli Zaretskii
2015-03-06 9:21 ` martin rudalics
2015-03-06 9:59 ` Ilya Zakharevich
2015-03-06 11:16 ` Eli Zaretskii
2015-03-07 1:44 ` Ilya Zakharevich
2015-03-07 9:11 ` Eli Zaretskii
2015-03-08 6:22 ` Ilya Zakharevich
2015-08-15 8:03 ` Eli Zaretskii
2015-08-15 11:22 ` Dani Moncayo
2015-08-15 11:38 ` Dani Moncayo
2015-08-15 12:10 ` Eli Zaretskii
2015-08-15 12:09 ` Eli Zaretskii
2015-08-15 12:24 ` Dani Moncayo
2015-08-15 12:26 ` Eli Zaretskii
2015-08-15 13:39 ` Dani Moncayo
2015-03-06 10:28 ` Eli Zaretskii
2015-03-06 14:13 ` Óscar Fuentes
2015-03-06 14:14 ` Óscar Fuentes
2015-03-06 14:40 ` Eli Zaretskii
2015-03-07 1:47 ` Ilya Zakharevich
2015-03-07 2:04 ` Óscar Fuentes
2015-03-07 9:19 ` Eli Zaretskii [this message]
2015-03-06 18:53 ` martin rudalics
2015-03-06 19:27 ` Eli Zaretskii
2015-03-07 9:40 ` martin rudalics
2015-03-07 10:04 ` Eli Zaretskii
2015-03-07 10:28 ` martin rudalics
2015-03-08 6:07 ` Ilya Zakharevich
2015-03-08 10:04 ` martin rudalics
2015-03-08 16:07 ` Ilya Zakharevich
2015-03-06 9:46 ` Ilya Zakharevich
2015-03-06 10:33 ` Eli Zaretskii
2015-03-07 1:37 ` Ilya Zakharevich
2015-03-06 10:08 ` Eli Zaretskii
2015-03-07 1:35 ` Ilya Zakharevich
2015-03-07 9:04 ` Eli Zaretskii
2015-03-08 6:14 ` Ilya Zakharevich
2015-03-08 15:46 ` Eli Zaretskii
2015-03-08 16:04 ` Ilya Zakharevich
2015-03-08 16:59 ` Eli Zaretskii
2015-03-03 21:15 ` Ilya Zakharevich
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=83d24lmafo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19989@debbugs.gnu.org \
--cc=ilya@math.berkeley.edu \
--cc=ofv@wanadoo.es \
/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).