From: "R. Diez" <rdiezmail-newlib@yahoo.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: [PATCH] libgloss: doc: generate single page & split html manuals
Date: Mon, 16 Oct 2023 09:31:38 +0000 (UTC) [thread overview]
Message-ID: <1541507901.13276384.1697448698591@mail.yahoo.com> (raw)
In-Reply-To: <20231015082206.32686-1-vapier@gentoo.org>
> By default, only split node html manuals are generated. Change the
> default to single page, and add an extra rule to also generate the
> split page manual.
I am a little confused about this patch, and I would like to learn more anyhow about the way Newlib generates its documentation.
> libgloss/Makefile.in | 11 +++++++++--
> libgloss/doc/Makefile.inc | 7 +++++++
Does this mean that only libgloss is affected? Or does the libc part also have the concept of split / single HTML manuals?
> +@HAVE_DOC_TRUE@html-local: doc/porting/index.html
Is 'html-local' the new target? If so, why not call it 'html-split' or 'html-split-node'? I am guessing that the default target is called 'html'.
On the other hand, if the old behaviour was to generate "split node html", why not just add a new target called 'html-single' or 'html-single-node'?
> +@HAVE_DOC_TRUE@AM_MAKEINFOFLAGS = --no-split
> [...]
> +@HAVE_DOC_TRUE@doc/porting/index.html: doc/porting.texi doc/$(am__dirstamp)
> +@HAVE_DOC_TRUE@ $(AM_V_GEN)$(MAKEINFOHTML) $(AM_MAKEINFOHTMLFLAGS) $(MAKEINFOFLAGS) \
> +@HAVE_DOC_TRUE@ --split=node $< -o $(@D)
> [...]
> +AM_MAKEINFOFLAGS = --no-split
> [...]
> +html-local: %D%/porting/index.html
> +%D%/porting/index.html: %D%/porting.texi %D%/$(am__dirstamp)
> + $(AM_V_GEN)$(MAKEINFOHTML) $(AM_MAKEINFOHTMLFLAGS) $(MAKEINFOFLAGS) \
> + --split=node $< -o $(@D)
I do not actually know what @HAVE_DOC_TRUE@ means. All I can see above next to AM_MAKEINFOFLAGS is "--no-split", but then the command-line arguments are both "--split=node". Is that not a contradiction?
Thanks in advance for your help,
rdiez
next prev parent reply other threads:[~2023-10-16 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 8:22 Mike Frysinger
2023-10-16 9:31 ` R. Diez [this message]
2023-10-16 10:16 ` Mike Frysinger
2023-10-16 13:44 ` R. Diez
2023-11-29 8:45 ` Mike Frysinger
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=1541507901.13276384.1697448698591@mail.yahoo.com \
--to=rdiezmail-newlib@yahoo.de \
--cc=newlib@sourceware.org \
--cc=vapier@gentoo.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.
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).