Do proper dependency tracking for doxygen
Status from this message: Applied, thanks
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | doc/api: generate dependency file for examples docdoc/ doc/ | +6 | 1 reply | |
| 2/2 | doc/api: track header files to rebuild docs on changedoc/ doc/ | +6 | 1 reply |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Luca Boccassi |
|---|---|
| 1/2 | A-b |
| 2/2 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [dpdk-dev] [PATCH 0/2] Do proper dependency tracking for doxygen
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(-)
Signature · 1 line
2.20.1