DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 0/2] Do proper dependency tracking for doxygen
Date: Fri, 17 Jan 2020 11:22:34 +0000	[thread overview]
Message-ID: <20200117112236.5225-1-bruce.richardson@intel.com> (raw)

When building doxygen docs as part of the build, there was no tracking
being done of the files processed, so that doxygen can be re-run if needed.
This patchset adds that tracking support, by generating a gcc-style
".d" file for the custom targets used in the doc/api build.

In doing so, we remove the doc directory as a custom target input path
directly, which removes a warning from meson.

Bruce Richardson (2):
  doc/api: generate dependency file for examples doc
  doc/api: track header files to rebuild docs on change

 doc/api/generate_doxygen.sh  | 5 ++++-
 doc/api/generate_examples.sh | 4 ++++
 doc/api/meson.build          | 8 ++++----
 3 files changed, 12 insertions(+), 5 deletions(-)

-- 
2.20.1


             reply	other threads:[~2020-01-17 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 11:22 Bruce Richardson [this message]
2020-01-17 11:22 ` [dpdk-dev] [PATCH 1/2] doc/api: generate dependency file for examples doc Bruce Richardson
2020-01-17 11:51   ` Luca Boccassi
2020-01-17 11:22 ` [dpdk-dev] [PATCH 2/2] doc/api: track header files to rebuild docs on change Bruce Richardson
2020-01-17 11:51   ` Luca Boccassi
2020-02-15 16:58 ` [dpdk-dev] [PATCH 0/2] Do proper dependency tracking for doxygen 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=20200117112236.5225-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --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).