From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v3 4/4] meson_options.txt: disable Sphinx by default
Date: Thu, 13 Apr 2023 11:21:59 +0200 [thread overview]
Message-ID: <20230413092159.146658-5-mauro.chehab@linux.intel.com> (raw)
In-Reply-To: <20230413092159.146658-1-mauro.chehab@linux.intel.com>
From: Mauro Carvalho Chehab <mchehab@kernel.org>
Building IGT with Sphinx enabled and rst2pdf installed takes:
$ touch tests/xe/xe_compute.c
$ time ninja -C build
...
real 0m10.545s
user 0m13.778s
sys 0m0.724s
With Sphinx disabled, the same build is a lot faster:
$ touch tests/xe/xe_compute.c
$ time ninja -C build
...
real 0m1.746s
user 0m1.574s
sys 0m0.171s
As Sphinx and PDF outputs aren't something that every single
IGT developer would need, let's speedup the build by disabling
it by default.
Test plan and test documentation validation will still run,
as this is a necessary step to validate if the tests documentation
were not broken on a patch, but this will save some time during
normal builds.
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
meson_options.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/meson_options.txt b/meson_options.txt
index d4e373d6cfc4..2cb44f20169b 100644
--- a/meson_options.txt
+++ b/meson_options.txt
@@ -26,6 +26,7 @@ option('testplan',
option('sphinx',
type : 'feature',
+ value : 'disabled',
description : 'Build testplan documentation using Sphinx')
option('docs',
--
2.39.2
next prev parent reply other threads:[~2023-04-13 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 9:21 [igt-dev] [PATCH i-g-t v3 0/4] ./scripts/igt_doc.py: speedup check logic Mauro Carvalho Chehab
2023-04-13 9:21 ` [igt-dev] [PATCH i-g-t v3 1/4] scripts/igt_doc.py: cleanup some pylint warnings Mauro Carvalho Chehab
2023-04-13 13:06 ` Kamil Konieczny
2023-04-13 9:21 ` [igt-dev] [PATCH i-g-t v3 2/4] scripts/igt_doc.py: don't depend on igt_runner anymore Mauro Carvalho Chehab
2023-04-13 13:07 ` Kamil Konieczny
2023-04-13 9:21 ` [igt-dev] [PATCH i-g-t v3 3/4] scripts/test_list.py: use a compiled regex for check Mauro Carvalho Chehab
2023-04-13 13:08 ` Kamil Konieczny
2023-04-13 9:21 ` Mauro Carvalho Chehab [this message]
2023-04-13 10:10 ` [igt-dev] [PATCH i-g-t v3 4/4] meson_options.txt: disable Sphinx by default Kamil Konieczny
2023-04-13 13:24 ` Mauro Carvalho Chehab
2023-04-21 15:37 ` Kamil Konieczny
2023-04-13 10:34 ` [igt-dev] ✓ Fi.CI.BAT: success for ./scripts/igt_doc.py: speedup check logic Patchwork
2023-04-13 12:01 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20230413092159.146658-5-mauro.chehab@linux.intel.com \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.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