From: Eli Zaretskii <eliz@gnu.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Making gnulib imports build on Windows
Date: Thu, 27 Jan 2011 10:13:16 -0500 [thread overview]
Message-ID: <E1PiTXA-00013q-36@fencepost.gnu.org> (raw)
In-Reply-To: <AANLkTi=xcZYKt9CwdapLBDp6LbMW8qYw8-eB+0GQUCmR@mail.gmail.com> (message from Lennart Borgman on Thu, 27 Jan 2011 15:34:16 +0100)
> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Thu, 27 Jan 2011 15:34:16 +0100
> Cc: emacs-devel@gnu.org
>
> On Thu, Jan 27, 2011 at 3:22 PM, Andy Moreton <andrewjmoreton@gmail.com> wrote:
> >
> > Sorry if I was unclear. Initially the w32 build needs to be repaired,
> > but the longer term aim should surely be reducing the differences
> > between w32 build scripts ans the rest of emacs. This includes allowing
> > for additional toolchains (e.g. Mingw-w64, llvm).
> >
> > Mingw32 and wingw-w64 cross toolchains are available in some Linux distros. If
> > developers on other platforms could at least build the win32 port, it
> > would make it easier for those developers to check whether their changes
> > break the w32 build. It might also simplify building tarballs and binary
> > releases.
>
> I agree that this might be good goals, but could please such
> development be kept in a separate branch, not on the trunk?
If you assume that this development (if indeed Andy decides to work on
it) will somehow get in the way of the native Windows build, then your
assumption is wrong. See my response to Andy.
next prev parent reply other threads:[~2011-01-27 15:13 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
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 [this message]
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
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=E1PiTXA-00013q-36@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@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).