From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id B22AFA04B5; Tue, 29 Sep 2020 18:55:51 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 76CA31DA61; Tue, 29 Sep 2020 18:55:18 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 208121D6F6 for ; Tue, 29 Sep 2020 18:55:13 +0200 (CEST) IronPort-SDR: xnGVnQK0RsamMhxBEZARA5LjWWKjfVhjLeDqv3r7hc2Z1ITZSSyg89JPf4dN/rOGrlkNyn7/Y1 om7LD0qocsNg== X-IronPort-AV: E=McAfee;i="6000,8403,9759"; a="159612222" X-IronPort-AV: E=Sophos;i="5.77,319,1596524400"; d="scan'208";a="159612222" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Sep 2020 09:55:11 -0700 IronPort-SDR: d0BFfUFPbyFwz8aq3id5fSy5HDeAUKzZ2VSxEiEeitxuMuQ4Pms3Tk0i3zykbFknT/iJ5RoeX6 UShcGqi4q7+w== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,319,1596524400"; d="scan'208";a="307833202" Received: from silpixa00399126.ir.intel.com ([10.237.222.4]) by orsmga003.jf.intel.com with ESMTP; 29 Sep 2020 09:55:10 -0700 From: Bruce Richardson To: dev@dpdk.org Cc: thomas@monjalon.net, Bruce Richardson Date: Tue, 29 Sep 2020 17:54:59 +0100 Message-Id: <20200929165502.336919-4-bruce.richardson@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20200929165502.336919-1-bruce.richardson@intel.com> References: <20200929153413.280581-1-bruce.richardson@intel.com> <20200929165502.336919-1-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH v2 3/6] doc/api: put output log file in build directory X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 --- 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