From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, "Ruifeng Wang" <ruifeng.wang@arm.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
david.marchand@redhat.com, bluca@debian.org
Subject: Re: [dpdk-dev] [PATCH 1/1] doc: fix build
Date: Tue, 26 Jan 2021 15:57:19 +0000 [thread overview]
Message-ID: <20210126155719.GF239@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <14391069.5Q96cbInNX@thomas>
On Tue, Jan 26, 2021 at 04:35:16PM +0100, Thomas Monjalon wrote:
> 26/01/2021 16:32, Bruce Richardson:
> > On Tue, Jan 26, 2021 at 04:07:22PM +0100, Thomas Monjalon wrote:
> > > When removing the label "arm_cross_build_getting_the_prerequisite_library"
> > > in the rework of cross_build_dpdk_for_arm64.rst,
> > > the reference to this section got broken.
> > > It went unnoticed because "ninja -C doc" does not regenerate the file
> > > which is referencing the changed file.
> > >
> > Do we know why this is? The doc builds should be doing proper dependency
> > tracking, based off the output from sphinx IIRC.
>
> It seems it is building only the changed files.
> I don't understand the logic in buildtools/call-sphinx-build.py
>
That needs some investigation, but it may be sphinx which is at fault
rather than the DPDK build. Most of the extra work done in the wrapper is
processing the files list worked by sphinx so we can mark them as
dependencies of the doc target. Sphinx itself does the incremental builds
of only changed files.
Unfortunately I don't have time to dig into this more right now.
next prev parent reply other threads:[~2021-01-26 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 15:07 Thomas Monjalon
2021-01-26 15:32 ` Bruce Richardson
2021-01-26 15:35 ` Thomas Monjalon
2021-01-26 15:57 ` Bruce Richardson [this message]
2021-01-26 15:32 ` David Marchand
2021-01-26 15:42 ` Thomas Monjalon
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=20210126155719.GF239@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=ruifeng.wang@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).