The meson documentation states that projects should not rely upon the
custom_target build commands are run from any given directory. Therefore,
rather than writing the standout output from doxygen to the current
directory - which could be anywhere in future, put it into the api
directory, so that it is in a known location.
Signed-off-by: Bruce Richardson <bruce.richard...@intel.com>
---
doc/api/generate_doxygen.sh | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/doc/api/generate_doxygen.sh b/doc/api/generate_doxygen.sh
index b4d66eb15..1350e5049 100755
--- a/doc/api/generate_doxygen.sh
+++ b/doc/api/generate_doxygen.sh
@@ -6,8 +6,10 @@ DOXYCONF=$1
OUTDIR=$2
SCRIPTCSS=$3
+OUT_FILE=$(dirname $OUTDIR)/doxygen.out
+
# run doxygen, capturing all the header files it processed
-doxygen "${DOXYCONF}" > doxygen.out
-echo "$OUTDIR: $(awk '/Preprocessing/ {printf("%s ", substr($2, 1, length($2)
- 3))}' doxygen.out)" > $OUTDIR.d
+doxygen "${DOXYCONF}" > $OUT_FILE
+echo "$OUTDIR: $(awk '/Preprocessing/ {printf("%s ", substr($2, 1, length($2)
- 3))}' $OUT_FILE)" > $OUTDIR.d
"${SCRIPTCSS}" "${OUTDIR}"/doxygen.css
--
2.25.1
