From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: bluca@debian.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH] build: skip processing docs folder if docs disabled
Date: Fri, 3 Jan 2020 14:46:13 +0000 [thread overview]
Message-ID: <20200103144613.2892178-1-bruce.richardson@intel.com> (raw)
While each target is set to be ignored if the docs are disabled in the
meson build, there is little reason to process the docs folder at all.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
doc/meson.build | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/meson.build b/doc/meson.build
index c5410d85d..c49ec8476 100644
--- a/doc/meson.build
+++ b/doc/meson.build
@@ -1,6 +1,10 @@
# SPDX-License-Identifier: BSD-3-Clause
# Copyright(c) 2018 Luca Boccassi <bluca@debian.org>
+if not get_option('enable_docs')
+ subdir_done()
+endif
+
doc_targets = []
doc_target_names = []
subdir('api')
--
2.24.1
next reply other threads:[~2020-01-03 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 14:46 Bruce Richardson [this message]
2020-02-16 10:07 ` Thomas Monjalon
2020-02-16 14:17 ` David Marchand
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=20200103144613.2892178-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.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).