From: Yonggang Luo <luoyonggang@gmail.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Yonggang Luo <luoyonggang@gmail.com>
Subject: [PATCH v3 0/4] Fixes docs building on msys2/mingw
Date: Fri, 16 Oct 2020 05:53:41 +0800 [thread overview]
Message-ID: <20201015215345.173-1-luoyonggang@gmail.com> (raw)
V2-V3
No need convert perl trick to python script anymore
after Paolo's removal of ninjatool.
Revise Meson: Move the detection logic for sphinx to meson
for pass other platform by letting SPHINX_ARGS to be empty
when build_docs are false
v1 - v2
Also move the docs configure part from
configure to meson, this also fixed the pending
ninjatool removal caused issue that docs can
not be build under msys2/mingw
Yonggang Luo (4):
docs: Fixes build docs on msys2/mingw
configure: the docdir option should passed to meson as is.
meson: Move the detection logic for sphinx to meson
cirrus: Enable doc build on msys2/mingw
.cirrus.yml | 6 +++-
configure | 62 +++--------------------------------
docs/conf.py | 2 +-
docs/meson.build | 4 +--
docs/sphinx/kerneldoc.py | 2 +-
meson.build | 59 +++++++++++++++++++++++++++++----
meson_options.txt | 5 ++-
tests/qapi-schema/meson.build | 2 +-
8 files changed, 71 insertions(+), 71 deletions(-)
--
2.28.0.windows.1
next reply other threads:[~2020-10-15 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 21:53 Yonggang Luo [this message]
2020-10-15 21:53 ` [PATCH v3 1/4] docs: Fixes build docs on msys2/mingw Yonggang Luo
2020-10-15 21:53 ` [PATCH v3 2/4] configure: the docdir option should passed to meson as is Yonggang Luo
2020-10-15 21:53 ` [PATCH v3 3/4] meson: Move the detection logic for sphinx to meson Yonggang Luo
2020-10-15 21:53 ` [PATCH v3 4/4] cirrus: Enable doc build on msys2/mingw Yonggang Luo
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=20201015215345.173-1-luoyonggang@gmail.com \
--to=luoyonggang@gmail.com \
--cc=pbonzini@redhat.com \
--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).