From: Mike Frysinger <vapier@gentoo.org>
To: "R. Diez" <rdiezmail-newlib@yahoo.de>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: [PATCH] libgloss: doc: generate single page & split html manuals
Date: Mon, 16 Oct 2023 16:01:25 +0545 [thread overview]
Message-ID: <ZS0NeeNmrZalsz82@vapier> (raw)
In-Reply-To: <1541507901.13276384.1697448698591@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]
On 16 Oct 2023 09:31, R. Diez wrote:
> > 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?
i'll update newlib (libc+libm) once people are happy with this direction.
> > +@HAVE_DOC_TRUE@html-local: doc/porting/index.html
>
> Is 'html-local' the new target?
this is an internal Automake hook point. people still run `make html` and
they'll get both forms of the manual.
https://www.gnu.org/software/automake/manual/1.16.5/automake.html#index-html_002dlocal
> > +@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.
Makefile.in is generated code that isn't meant to be read by most people.
> 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?
standard CLI behavior: later options override earlier one.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-16 10:16 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
2023-10-16 10:16 ` Mike Frysinger [this message]
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=ZS0NeeNmrZalsz82@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.org \
--cc=rdiezmail-newlib@yahoo.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.
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).