From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: "nmake info" Windows patch
Date: Sat, 22 Feb 2003 11:21:55 +0200 [thread overview]
Message-ID: <3405-Sat22Feb2003112154+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <u7kbti5vn.fsf@runestig.com> (peter@runestig.com)
> From: "Peter 'Luna' Runestig" <peter@runestig.com>
> Date: 22 Feb 2003 00:14:04 +0100
>
> "Peter 'Luna' Runestig" <peter@runestig.com> writes:
> > Here is another thing I mentioned on bug-gnu-emacs some time ago. This
> > patch that adds the `info' target to the Windows build. Tested with
> > MSVC6/CygWin 1.3.20.
> > ftp://ftp.runestig.com/pub/emacs/emacs-20030219-makeinfo.patch
> > http://ftp.runestig.com/pub/emacs/emacs-20030219-makeinfo.patch
>
> By request, I'm actually posting the patch here. I take it it's the
> preferred way in this forum then. You never now, sometimes people bitch
> over a sig > four lines...
> [...]
> +SHELL = cmd
> [...]
> +MAKEINFO = makeinfo
> +TEXI2DVI = texi2dvi
> +DVIPS = dvips
> +ENVADD = TEXINPUTS="$(srcdir):$(TEXINPUTS)" MAKEINFO="$(MAKEINFO) -I$(srcdir)"
> [...]
> +emacs-lisp-intro.dvi: $(INFO_SOURCES)
> + $(ENVADD) $(TEXI2DVI) $(srcdir)/emacs-lisp-intro.texi
Does this really work in native Windows environment (i.e. without
Cygwin being installed)? I don't think CMD.EXE can run Unix shell
scripts such as texi2dvi, and neither I think that a native Windows
port of makeinfo will DTRT with the value of TEXINPUTS where
directories are separated by colons (instead of semi-colons).
If this only works with Cygwin tools, we should at least tell that
somewhere. What would be _really_ nice if at least some targets would
work with native Windows tools, not only with Cygwin. For example:
> +mostlyclean:
> + rm -f *.log *.cp *.fn *.ky *.pg *.vr *.tp
> +
> +clean: mostlyclean
> + rm -f *.dvi
There's no reason not to use CMD's built-in DEL command here (perhaps
with a FOR loop).
> +++ emacs-20030219/nt/makefile.w32-in 2003-02-21 21:23:01.000000000 +0100
> @@ -214,6 +214,15 @@
> $(MAKE) $(MFLAGS) -C ../lisp install
> $(MAKE) $(MFLAGS) -C ../leim install
>
> +force-info:
> +# Note that man/makefile knows how to
> +# put the info files in $(srcdir),
> +# so we can do ok running make in the build dir.
> +info: force-info
> + (cd ..\man && $(MAKE) $(MFLAGS) info)
> + (cd ..\lispref && $(MAKE) $(MFLAGS) info)
> + (cd ..\lispintro && $(MAKE) $(MFLAGS) info)
This also won't work except with Cygwin Bash (or some other ported
Unix shell) as your shell.
Apologies if I missed some of this thread earlier, which stated that
the intent is indeed to make this work with Cygwin only.
next prev parent reply other threads:[~2003-02-22 9:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 21:54 "nmake info" Windows patch Peter 'Luna' Runestig
2003-02-21 23:14 ` Peter 'Luna' Runestig
2003-02-22 9:21 ` Eli Zaretskii [this message]
2003-02-22 9:53 ` Peter 'Luna' Runestig
2003-02-22 11:40 ` Juanma Barranquero
2003-02-22 19:08 ` Eli Zaretskii
2003-05-20 9:08 ` Peter 'Luna' Runestig
2003-05-20 11:14 ` Jason Rumney
2003-05-20 13:10 ` Juanma Barranquero
2003-02-22 19:11 ` Eli Zaretskii
2003-02-22 21:46 ` Jason Rumney
2003-02-22 10:13 ` Jason Rumney
2003-02-22 19:11 ` Eli Zaretskii
2003-02-22 21:44 ` Jason Rumney
-- strict thread matches above, loose matches on Subject: below --
2003-08-15 16:04 Your Emacs changes Richard Stallman
2003-08-18 15:21 ` Peter 'Luna' Runestig
2003-08-19 7:51 ` Eli Zaretskii
2003-08-19 7:59 ` Peter 'Luna' Runestig
2003-08-19 17:46 ` Eli Zaretskii
2003-08-29 7:25 ` "nmake info" Windows patch (was: Your Emacs changes) Peter 'Luna' Runestig
2003-08-29 11:20 ` Eli Zaretskii
2003-08-29 11:35 ` "nmake info" Windows patch Peter 'Luna' Runestig
2003-08-29 15:11 ` Eli Zaretskii
2003-08-30 3:10 ` Richard Stallman
2003-05-20 11:28 Peter 'Luna' Runestig
2002-09-03 7:42 Peter 'Luna' Runestig
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=3405-Sat22Feb2003112154+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--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.