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 90A55A04BC; Tue, 29 Sep 2020 17:34:26 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DBB401C299; Tue, 29 Sep 2020 17:34:22 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 808EF1BFE5 for ; Tue, 29 Sep 2020 17:34:21 +0200 (CEST) IronPort-SDR: /z9Sg5+BbzojneHgJEyuXWfPs6oJB0Cj8kYxTFafTQrgCBuuOIIB9ReOshFPoPOWidZ7BK+KuB Py8KPouNA5YA== X-IronPort-AV: E=McAfee;i="6000,8403,9759"; a="223809925" X-IronPort-AV: E=Sophos;i="5.77,319,1596524400"; d="scan'208";a="223809925" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Sep 2020 08:34:19 -0700 IronPort-SDR: 0AyWVgspjmCJLGAkebWcDdmYaI0yJCBXztA+JC/ri8/AQQMotEE5RaYSuE/FT68yy9/wVC9GB/ XSLjOCRSKrEQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,319,1596524400"; d="scan'208";a="514726410" Received: from silpixa00399126.ir.intel.com ([10.237.222.4]) by fmsmga005.fm.intel.com with ESMTP; 29 Sep 2020 08:34:18 -0700 From: Bruce Richardson To: dev@dpdk.org Cc: thomas@monjalon.net, Bruce Richardson Date: Tue, 29 Sep 2020 16:34:09 +0100 Message-Id: <20200929153413.280581-1-bruce.richardson@intel.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH 0/4] improve output when building docs 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" When building the documentation, a lot of text is output, meaning that any warnings can be missed in all the text. Unfortunately, ninja merges both stderr and stdout of all tasks so one cannot just redirect stdout to a separate location as part of the build command to rectify that. Therefore, since we rarely care about the output of the doc builds, only output the stderr text and write the standard output text to a log file in the relevant build folder (i.e. build/doc/guides or build/doc/api) Bruce Richardson (4): doc/api: hide verbose doxygen standard output doc/api: align output folder with sphinx guides doc/api: put output log file in build directory doc/guides: suppress printing out standard output buildtools/call-sphinx-build.py | 6 ++++-- doc/api/generate_doxygen.sh | 6 ++++-- doc/api/meson.build | 6 +++--- 3 files changed, 11 insertions(+), 7 deletions(-) -- 2.25.1