Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>,
	Carlos O'Donell <carlos@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Use makeinfo --html for HTML manuals
Date: Sat, 18 Apr 2009 16:36:00 -0000	[thread overview]
Message-ID: <83iql1j4wi.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0904172038520.12227@digraph.polyomino.org.uk>

> Date: Fri, 17 Apr 2009 20:40:20 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
> 
> This patch makes the GDB makefiles build HTML manuals using makeinfo
> --html instead of texi2html.

Thanks.  I'm okay with this change, but I have one comment.

> +gdb/index.html: ${GDB_DOC_FILES}
>  	$(MAKEHTML) $(MAKEHTMLFLAGS) -I ${READLINE_DIR} -I ${GDBMI_DIR} -I $(srcdir) $(srcdir)/gdb.texinfo
>  
>  # Clean these up before each run.  Avoids a catch 22 with not being
> @@ -445,7 +456,7 @@
>  
>  # GDB INTERNALS MANUAL: HTML file
>  
> -gdbint_toc.html: $(GDBINT_DOC_FILES)
> +gdbint/index.html: $(GDBINT_DOC_FILES)
>  	$(MAKEHTML) $(MAKEHTMLFLAGS) $(srcdir)/gdbint.texinfo
>  
>  stabs.info: $(STABS_DOC_FILES)
> @@ -453,7 +464,7 @@
>  
>  # STABS DOCUMENTATION: HTML file
>  
> -stabs_toc.html: $(STABS_DOC_FILES)
> +stabs/index.html: $(STABS_DOC_FILES)
>  	$(MAKEHTML) $(MAKEHTMLFLAGS) $(srcdir)/stabs.texinfo
>  
>  # Clean these up before each run.  Avoids a catch 22 with not being
> @@ -495,7 +506,7 @@
>  annotate.info: $(ANNOTATE_DOC_FILES)
>  	$(MAKEINFO)  -I $(srcdir) -o annotate.info $(srcdir)/annotate.texinfo
>  
> -annotate_toc.html: $(ANNOTATE_DOC_FILES)
> +annotate/index.html: $(ANNOTATE_DOC_FILES)
>  	$(MAKEHTML) $(MAKEHTMLFLAGS) $(srcdir)/annotate.texinfo

Why the discrepancy wrt the use of the -I $(srcdir) switch between the
commands for different manuals?  I'd prefer them all to use that
switch, even if some of them do not @include any other files, to avoid
surprises if we some day add such directives.

Btw, I hear that the next release of Texinfo will ditch makeinfo the C
program and use texi2html instead.  (There probably will still be a
wrapper shell script called `makeinfo', for backward compatibility.)
What that will do to all this, is anybody's guess.  But we don't need
to worry about this today.


  parent reply	other threads:[~2009-04-18 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 20:40 Joseph S. Myers
2009-04-17 21:02 ` Michael Snyder
2009-04-18 16:36 ` Eli Zaretskii [this message]
2009-04-18 17:15   ` Joseph S. Myers
2009-04-20 19:23     ` Carlos O'Donell

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=83iql1j4wi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=carlos@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox