From: Thomas Monjalon <thomas@monjalon.net>
To: luca.boccassi@gmail.com
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] doc: add install_tag to meson
Date: Tue, 25 Nov 2025 02:22:39 +0100 [thread overview]
Message-ID: <3862772.88bMQJbFj6@thomas> (raw)
In-Reply-To: <Z3uwcddSVFDt6dNn@bricha3-mobl1.ger.corp.intel.com>
06/01/2025 11:29, Bruce Richardson:
> On Mon, Dec 23, 2024 at 01:21:13PM +0000, luca.boccassi@gmail.com wrote:
> > From: "bluca@debian.org" <bluca@debian.org>
> >
> > This allows building and installing only the documentation, without
> > recompiling the whole project, using:
> >
> > meson build -Denable_docs=true
> > meson compile -C build doc
> > meson install -C build --no-rebuild --tags doc
> >
> > In Debian/Ubuntu the documentation is built separately from the binaries,
> > in a separate architecture-independent build job, so that it has to be
> > done only once, instead of once per supported architecture.
> >
> > Signed-off-by: Luca Boccassi <bluca@debian.org>
> > ---
> > This requires meson 0.60, so there's a warning printed as the minimum
> > defined is 0.57, but it's harmless, and the feature is only used when
> > explicitly invoked with --tags, which simply has to be done with newer
> > meson versions. If install --tags is not used, then there's no issue.
> >
> > doc/api/meson.build | 3 +++
> > doc/guides/meson.build | 1 +
> > 2 files changed, 4 insertions(+)
> >
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
This patch was missed.
Applied, thanks.
prev parent reply other threads:[~2025-11-25 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 13:21 [PATCH] doc: add install_tag to meson luca.boccassi
2025-01-06 10:29 ` Bruce Richardson
2025-11-21 12:41 ` Luca Boccassi
2025-11-25 1:22 ` Thomas Monjalon [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=3862772.88bMQJbFj6@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=luca.boccassi@gmail.com \
/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).