From: "Marc Poulhiès" <poulhies@adacore.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Joseph Myers <joseph@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/3] Add generated .opt.urls files
Date: Mon, 13 Nov 2023 17:02:09 +0100 [thread overview]
Message-ID: <87y1f18wk5.fsf@adacore.com> (raw)
In-Reply-To: <24d0411f5e8494cf3c6b58bd1b259bf07fcfa858.camel@redhat.com>
David Malcolm <dmalcolm@redhat.com> writes:
>
> The new regenerate-opt-urls.py script only parsed
> buildir/gcc/HTML/gcc-14.0.0/gcc/Option-Index.html
> looking for anchors for options via a regex.
>
> Looking at my build, I don't see any generated Ada HTML docs, so maybe
> I messed this up? Does the generated HTML from the generated Ada
> texinfo go somewhere else? (and, in particular, does it have its own
> index?)
>
> Perhaps this script could also deal directly with Sphinx-generated
> HTML?
I investigated a bit... The Ada part doesn't handle the html target, so
it's expected you don't have anything to parse. The online docs are
generated using a different script, not using these makefiles.
I'll see if I can fix the html target for ada, so that your script
doesn't need to be changed :)
>> We are generating the texinfo files
>> from sphinx, so maybe we could adjust the script to also match what
>> the
>> sphinx generator produces?
>
> It *might* be as simple as pointing it at the option index for the
> generated HTML for Ada.
That's worth a try, when/if I can fix the HTML target.
Marc
next prev parent reply other threads:[~2023-11-13 16:09 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 21:42 [PATCH 0/3] Option handling: add documentation URLs David Malcolm
2023-11-10 21:42 ` [PATCH 1/3] options: add gcc/regenerate-opt-urls.py David Malcolm
2023-11-10 21:42 ` [PATCH 2/3] Add generated .opt.urls files David Malcolm
2023-11-12 10:56 ` Iain Buclaw
2023-11-13 14:07 ` David Malcolm
2023-11-13 13:11 ` Marc Poulhiès
2023-11-13 14:07 ` David Malcolm
2023-11-13 16:02 ` Marc Poulhiès [this message]
2023-12-19 14:47 ` Marc Poulhiès
2023-11-10 21:42 ` [PATCH 3/3] diagnostics: use the .opt.urls files to urlify quoted text David Malcolm
2023-11-14 17:44 ` Arthur Cohen
2023-11-14 0:12 ` [PATCH 0/3] Option handling: add documentation URLs Joseph Myers
2023-11-15 22:50 ` David Malcolm
2023-11-15 23:40 ` Joseph Myers
2023-11-16 14:28 ` [PATCH 0/4] v2 of " David Malcolm
2023-11-16 14:28 ` [PATCH 1/4] options: add gcc/regenerate-opt-urls.py David Malcolm
2023-11-16 14:28 ` [PATCH 2/4] Add generated .opt.urls files David Malcolm
2023-11-16 14:28 ` [PATCH 3/4] opts: add logic to generate options-urls.cc David Malcolm
2023-11-16 14:28 ` [PATCH 4/4] options: wire up options-urls.cc into gcc_urlifier David Malcolm
2023-11-21 1:09 ` [PATCH 0/4] v2 of Option handling: add documentation URLs Hans-Peter Nilsson
2023-11-21 13:57 ` David Malcolm
2023-11-21 14:12 ` Tobias Burnus
2023-11-21 15:23 ` David Malcolm
2023-11-21 23:43 ` Joseph Myers
2023-12-08 23:35 ` David Malcolm
2023-12-10 23:35 ` Mark Wielaard
2023-12-14 15:01 ` [PATCH 0/4] v3 of: " David Malcolm
2023-12-14 15:01 ` [PATCH 1/4; v3] options: add gcc/regenerate-opt-urls.py David Malcolm
2023-12-20 0:24 ` Joseph Myers
2023-12-14 15:01 ` [PATCH 2/4; v3] Add generated .opt.urls files David Malcolm
2023-12-14 15:01 ` [PATCH 3/4; v2] opts: add logic to generate options-urls.cc David Malcolm
2023-12-14 15:01 ` [PATCH 4/4; v2] options: wire up options-urls.cc into gcc_urlifier David Malcolm
2023-12-15 0:59 ` [PATCH 0/4] v3 of: Option handling: add documentation URLs Mark Wielaard
2023-12-15 14:47 ` David Malcolm
2024-01-04 14:57 ` CI for "Option handling: add documentation URLs" David Malcolm
2024-02-18 22:58 ` Mark Wielaard
2024-02-19 11:38 ` Mark Wielaard
2024-02-22 3:57 ` YunQiang Su
2024-02-24 17:42 ` Mark Wielaard
2024-03-03 20:04 ` Mark Wielaard
2024-03-04 13:48 ` David Malcolm
2024-03-05 12:06 ` Mark Wielaard
2024-03-05 13:34 ` David Malcolm
2024-03-05 20:24 ` Mark Wielaard
2024-03-15 7:33 ` YunQiang Su
2024-03-15 10:06 ` Mark Wielaard
2023-12-20 0:28 ` [PATCH 0/4] v3 of: Option handling: add documentation URLs Joseph Myers
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=87y1f18wk5.fsf@adacore.com \
--to=poulhies@adacore.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).