From: "Robin Jarry" <rjarry@redhat.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>
Cc: dev@dpdk.org, "Jeremy Spewock" <jspewock@iol.unh.edu>,
"Luca Vizzarro" <luca.vizzarro@arm.com>,
"Dean Marx" <dmarx@iol.unh.edu>,
"Thomas Monjalon" <thomas@monjalon.net>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: Re: [PATCH dpdk] meson: properly disable docs
Date: Tue, 22 Oct 2024 17:31:47 +0200 [thread overview]
Message-ID: <D52FYTIW9FKK.LWWP0Q5K3ZV7@redhat.com> (raw)
In-Reply-To: <ZxfD8XQvEiwc1Qz1@bricha3-mobl1.ger.corp.intel.com>
Bruce Richardson, Oct 22, 2024 at 17:25:
> No strong objection to this. Just FYI, the reason it is currently done as
> it is in the build, is that even if you configure a build without the docs
> enabled, you can just build the docs explicitly by doing "ninja -C build
> doc". That is so that one can do a test build of the docs without
> a) having to reconfigure the whole project
> b) not have every build from then on rebuild e.g. the APIs doc if you
> change a header.
Oh, I didn't know it was on purpose. I was surprised to see doc related
warnings with -Denable_docs=false.
Feel free to disregard this patch if you think it is too drastic.
next prev parent reply other threads:[~2024-10-22 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 15:11 Robin Jarry
2024-10-22 15:25 ` Bruce Richardson
2024-10-22 15:31 ` Robin Jarry [this message]
2024-10-22 15:49 ` Bruce Richardson
2024-10-22 16:01 ` Thomas Monjalon
2024-10-22 15:36 ` Stephen Hemminger
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=D52FYTIW9FKK.LWWP0Q5K3ZV7@redhat.com \
--to=rjarry@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=luca.vizzarro@arm.com \
--cc=thomas@monjalon.net \
/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).