unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Martin Stemplinger <mstemplinger@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Making gnulib imports build on Windows
Date: Fri, 28 Jan 2011 16:30:28 +0200	[thread overview]
Message-ID: <8362t9hzi3.fsf@gnu.org> (raw)
In-Reply-To: <81y666qe8s.fsf@gmx.de>

> From: Martin Stemplinger <mstemplinger@gmx.de>
> Date: Thu, 27 Jan 2011 21:32:35 +0100
> 
> > And those who hate cygwin can get gnuwin32.
> 
> Gnuwin is needed anyway if you want image support. So at least for me
> it would be no big deal to install also the sed package from gnuwin to
> build. But I only talk about the windows build on XP, vista and
> windows 7 not about the MS-DOS build that Eli also maintains. Things
> may be completely different there.

Things _are_ completely different with the MS-DOS port: Sed is already
required to build it.  And, unlike with GnuWin32, the DOS
(a.k.a. DJGPP) port of Sed is rock-solid and up to date (as generally
are all the other DJGPP ports of GNU software).

As for requiring Sed for the Windows build: those who don't mind
installing it will be at advantage, in that they will be able to
regenerate getopt.h whenever a new version of getopt.in.h gets
imported from gnulib.  Those who don't have Sed will have to wait for
someone who does to update the repository with the regenerated files.

> E.g. make dist is currently broken because some of the
> files like BUGS, COPYING, README, INSTALL are not copied to the
> install dir. At least I alsways need to copy those manually after make
> install for make dist to succeed.

Please submit bug reports about any such omissions, thanks.

> > I have made this suggestion in the past and I know that Eli does not
> > like it. However, I am making it again here so that in a few years, when
> > Eli inevitably sees the light and relents, I can say "I told you so"
> > (provided I am still around :-).
> Eli has probably struggled a lot to get the various windows versions
> to work and I really appreciate this very much because it helps me to
> have the true editor also on windows. 

Thanks, but the credit is not mine to take.  The current build system
on Windows was done by others (see nt/ChangeLog), I'm just trying not
to break it ;-)



      reply	other threads:[~2011-01-28 14:30 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
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 [this message]

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=8362t9hzi3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mstemplinger@gmx.de \
    /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).