From: Gerald Pfeifer <gerald@pfeifer.com>
To: Gaius Mulley <gaiusmod2@gmail.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: Fri, 17 Mar 2023 00:22:33 +0100 (CET) [thread overview]
Message-ID: <3cb001e9-ed1e-4a0c-4db8-9bc7e8bc9539@pfeifer.com> (raw)
In-Reply-To: <87pm99b96l.fsf@debian>
On Thu, 16 Mar 2023, Gaius Mulley wrote:
>> Does maintainer-scripts/update_web_docs_git require an update to cover
>> Modula-2 and actually build the manual we are now linking to
> 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.
I sorted the special casing alphabetically and pushed the updated patch
below.
Then I updated the script on gcc.gnu.org and did a testrun.
Indeed Modula 2 manuals are now available below
https://gcc.gnu.org/onlinedocs/
just the links from that page are off (referring to m2 instead of gm2).
I'll fix that next.
Gerald
commit fa4d0ab533cc2bc9cb6f512b3d4bd0bbc01ee797
Author: Gaius Mulley <gaiusmod2@gmail.com>
Date: Fri Mar 17 00:08:20 2023 +0100
maintainer-scripts: Add Modula-2 manual to update_web_docs_git
maintainer-scripts/ChangeLog:
* update_web_docs_git (MANUALS): Add gm2.
Add include path for gm2 manual.
diff --git a/maintainer-scripts/update_web_docs_git b/maintainer-scripts/update_web_docs_git
index 1c6a993cafd..4bb4897bf35 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
@@ -167,7 +168,10 @@ for file in $MANUALS; do
filename=`find . -name ${file}.texi`
if [ "${filename}" ]; then
includes="-I ${includedir} -I `dirname ${filename}`"
- if [ "$file" = "gnat_ugn" ]; then
+ if [ "$file" = "gm2" ]; then
+ includes="$includes -I gcc/gcc/m2/target-independent"
+ includes="$includes -I gcc/gcc/m2/target-independent/m2"
+ elif [ "$file" = "gnat_ugn" ]; then
includes="$includes -I gcc/gcc/ada -I gcc/gcc/ada/doc/gnat_ugn"
fi
makeinfo --html --css-ref $CSS $includes -o ${file} ${filename}
prev parent reply other threads:[~2023-03-16 23:22 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
2023-03-16 23:22 ` Gerald Pfeifer [this message]
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=3cb001e9-ed1e-4a0c-4db8-9bc7e8bc9539@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).