From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH] docs/sphinx/qapidoc.py: Handle change of QAPI's builtin module name
Date: Mon, 15 Feb 2021 13:10:23 -0500 [thread overview]
Message-ID: <492a45e2-adc3-9364-a141-076f1fc90cb0@redhat.com> (raw)
In-Reply-To: <20210212161311.28915-1-peter.maydell@linaro.org>
On 2/12/21 11:13 AM, Peter Maydell wrote:
> In commit e2bbc4eaa7f0 we changed the QAPI modules to name the built-in
> module "./builtin" rather than None, but forgot to update the Sphinx
> plugin. The effect of this was that when the plugin generated a dependency
> file it was including a bogus dependency on a non-existent file named
> "builtin", which meant that ninja would run Sphinx and rebuild all
> the documentation every time even if nothing had changed.
>
> Update the plugin to use the new name of the builtin module.
>
> Fixes: e2bbc4eaa7f0
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> docs/sphinx/qapidoc.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/docs/sphinx/qapidoc.py b/docs/sphinx/qapidoc.py
> index e03abcbb959..b7b86b5dffb 100644
> --- a/docs/sphinx/qapidoc.py
> +++ b/docs/sphinx/qapidoc.py
> @@ -464,7 +464,7 @@ class QAPISchemaGenDepVisitor(QAPISchemaVisitor):
> self._qapidir = qapidir
>
> def visit_module(self, name):
> - if name is not None:
> + if name != "./builtin":
> qapifile = self._qapidir + '/' + name
> self._env.note_dependency(os.path.abspath(qapifile))
> super().visit_module(name)
>
Reviewed-by: John Snow <jsnow@redhat.com>
prev parent reply other threads:[~2021-02-15 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 16:13 [PATCH] docs/sphinx/qapidoc.py: Handle change of QAPI's builtin module name Peter Maydell
2021-02-12 16:26 ` Paolo Bonzini
2021-02-12 16:51 ` Eric Blake
2021-02-15 16:07 ` Peter Maydell
2021-02-15 18:10 ` John Snow [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=492a45e2-adc3-9364-a141-076f1fc90cb0@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).