From: Andy Moreton <andrewjmoreton@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Making gnulib imports build on Windows
Date: Wed, 26 Jan 2011 22:40:30 +0000 [thread overview]
Message-ID: <82lj27p9up.fsf@gmail.com> (raw)
In-Reply-To: 83vd1bwjig.fsf@gnu.org
On Wed 26 Jan 2011, Eli Zaretskii wrote:
> Until now, building Emacs for Windows did not require Sed. I see the
> following possible ways to deal with this:
[...]
> I don't like asking every end user to have Sed, especially since many
> Windows ports of Sed are notoriously broken (I had to port it myself
> to get a reliable tool). And since 3) sounds like wheel reinvention,
> I tend to alternative 2).
>
> Comments and ideas are welcome.
Although Cygwin and MSYS are widely used for building emacs for Windows,
I agree that option 2) is the best. The maintainer-only rules
for generating the pre-canned configuration and headers should minimise
the doffernces from the standard POSIX makefile infrastructure as far as
possible.
In a perfect world, this would allow the use of mingw32 or mingw-w64
cross compilers to build Windows emacs binaries on POSIX hosts.
What can I do to help this happen ?
AndyM
next prev parent reply other threads:[~2011-01-26 22:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 19:29 Making gnulib imports build on Windows Eli Zaretskii
2011-01-26 21:48 ` Paul Eggert
2011-01-27 4:04 ` Eli Zaretskii
2011-01-26 22:40 ` Andy Moreton [this message]
2011-01-27 4:08 ` Eli Zaretskii
2011-01-27 14:22 ` Andy Moreton
2011-01-27 14:32 ` Eli Zaretskii
2011-01-27 15:36 ` Andy Moreton
2011-01-27 14:34 ` Lennart Borgman
2011-01-27 15:13 ` Eli Zaretskii
2011-01-27 15:15 ` Lennart Borgman
2011-01-27 16:43 ` Sam Steingold
2011-01-27 16:58 ` Lennart Borgman
2011-01-27 17:28 ` Sam Steingold
2011-01-27 20:13 ` Juanma Barranquero
2011-01-28 13:08 ` martin rudalics
2011-01-28 15:12 ` Sam Steingold
2011-01-28 15:20 ` Juanma Barranquero
2011-01-28 17:32 ` Sean Sieger
2011-01-28 19:30 ` Sam Steingold
2011-01-28 20:44 ` Martin Stemplinger
2011-01-28 20:49 ` Lennart Borgman
2011-01-27 20:32 ` Martin Stemplinger
2011-01-28 14:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82lj27p9up.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.