From: Sam Steingold <sds@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: cannot build on w32
Date: Wed, 19 Jan 2011 11:16:52 -0500 [thread overview]
Message-ID: <AANLkTimwrACzNO3UzofGQ+YGSV3xzEHZ+4+f3PxceSzg@mail.gmail.com> (raw)
In-Reply-To: <E1PfabL-0002vx-1D@fencepost.gnu.org>
On Wed, Jan 19, 2011 at 11:09 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 19 Jan 2011 11:05:26 -0500
>> From: Sam Steingold <sds@gnu.org>
>> Cc: emacs-devel@gnu.org
>>
>> fwiw, I use gnulib modules in clisp on both windows and unix and I use
>> the same autoconf-created configure files on unix and windows alike
>> identically.
>> (except that I to "./configure CC='gcc -mno-cygwin'" on win32).
>> this saves me an extra effort of maintaining a separate build system on windows.
>
> Sorry, requiring Emacs users on Windows install Cygwin just to build
> Emacs is out of question.
1. you don't need cygwin, just mingw.
2. people who _build_ emacs themselves usually already have cygwin
> (And for building on a single platform, autoconf is overkill anyway, IMO.)
that's what autoconf is for: so that you do not have to have a
separate build systems for various platforms.
it is weird to use autoconf for some platforms but not others.
--
Sam Steingold <http://sds.podval.org>
next prev parent reply other threads:[~2011-01-19 16:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 15:12 cannot build on w32 Sam Steingold
2011-01-19 15:18 ` Tom Tromey
2011-01-19 15:33 ` Sam Steingold
2011-01-19 15:53 ` Sam Steingold
2011-01-19 16:03 ` Eli Zaretskii
2011-01-19 16:14 ` Sam Steingold
2011-01-19 16:32 ` Eli Zaretskii
2011-01-19 16:05 ` Sam Steingold
2011-01-19 16:09 ` Eli Zaretskii
2011-01-19 16:16 ` Sam Steingold [this message]
2011-01-19 16:39 ` Eli Zaretskii
2011-01-19 17:36 ` Sam Steingold
2011-01-19 19:01 ` Jan Djärv
2011-01-20 15:17 ` Sam Steingold
2011-01-20 15:27 ` Eli Zaretskii
2011-01-20 18:46 ` Sam Steingold
2011-01-20 14:12 ` Richard Stallman
2011-01-20 14:50 ` Sam Steingold
2011-01-20 15:00 ` Eli Zaretskii
2011-01-21 20:15 ` Richard Stallman
2011-01-19 16:21 ` Óscar Fuentes
2011-01-19 16:41 ` Eli Zaretskii
2011-01-19 16:52 ` Óscar Fuentes
2011-01-19 15:36 ` Andreas Schwab
2011-01-19 15:40 ` Tom Tromey
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=AANLkTimwrACzNO3UzofGQ+YGSV3xzEHZ+4+f3PxceSzg@mail.gmail.com \
--to=sds@gnu.org \
--cc=eliz@gnu.org \
--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 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).