From: Gaius Mulley <gaiusmod2@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org,
Richard Guenther <richard.guenther@gmail.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [wwwdocs] document modula-2 in gcc-13/changes.html (and index.html)
Date: Thu, 16 Mar 2023 04:40:34 +0000 [thread overview]
Message-ID: <87pm99b96l.fsf@debian> (raw)
In-Reply-To: <a9ee1e43-b91c-938e-f562-8a6ee52758a7@pfeifer.com> (Gerald Pfeifer's message of "Wed, 15 Mar 2023 23:51:34 +0100 (CET)")
Gerald Pfeifer <gerald@pfeifer.com> writes:
> The patch is now in, alas all the GNU M2 manual links now point to
> non-existant locations.
>
> Does maintainer-scripts/update_web_docs_git require an update to cover
> Modula-2 and actually build the manual we are now linking to (or rather
> trying to)?
>
> Gerald
Apologies I was going to ask about these links. I've updated the m2
subtree with target documentation independent sections. Attached is a
proposed patch for maintainer-scripts/update_web_docs_git feel free to
apply or adapt in any way.
regards,
Gaius
--->o--->o--->o--->o--->o--->o--->o--->o--->o--->o--->o--->o--->o--->o
Add modula-2 documentation to be built
Update the online documentation build script to include modula-2.
maintainer-scripts/ChangeLog:
* update_web_docs_git (MANUALS): Add gm2.
Add include path for m2 target independent sections.
diff --git a/maintainer-scripts/update_web_docs_git b/maintainer-scripts/update_web_docs_git
index 1c6a993cafd..c678fc29155 100755
--- a/maintainer-scripts/update_web_docs_git
+++ b/maintainer-scripts/update_web_docs_git
@@ -24,6 +24,7 @@ MANUALS="cpp
gdc
gfortran
gfc-internals
+ gm2
gnat_ugn
gnat-style
gnat_rm
@@ -169,6 +170,9 @@ for file in $MANUALS; do
includes="-I ${includedir} -I `dirname ${filename}`"
if [ "$file" = "gnat_ugn" ]; then
includes="$includes -I gcc/gcc/ada -I gcc/gcc/ada/doc/gnat_ugn"
+ elif [ "$file" = "gm2" ]; then
+ includes="$includes -I gcc/gcc/m2/target-independent"
+ includes="$includes -I gcc/gcc/m2/target-independent/m2"
fi
makeinfo --html --css-ref $CSS $includes -o ${file} ${filename}
tar cf ${file}-html.tar ${file}/*.html
next prev parent reply other threads:[~2023-03-16 4:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 14:52 Gaius Mulley
2023-02-03 15:28 ` Jakub Jelinek
2023-02-03 19:18 ` Gerald Pfeifer
2023-02-06 11:05 ` Gaius Mulley
2023-03-04 7:14 ` Gerald Pfeifer
2023-03-06 11:40 ` Gaius Mulley
2023-03-15 22:51 ` Gerald Pfeifer
2023-03-16 4:40 ` Gaius Mulley [this message]
2023-03-16 23:22 ` Gerald Pfeifer
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=87pm99b96l.fsf@debian \
--to=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).