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 34CCDA04DD; Thu, 22 Oct 2020 17:00:26 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 44283AA15; Thu, 22 Oct 2020 17:00:05 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 64FFEAA05 for ; Thu, 22 Oct 2020 17:00:02 +0200 (CEST) IronPort-SDR: p6rXMpfcqmJbK5x98wRvgbFl7hHb6A+QibTOySybnKIBNXgJmmry+irGldn6h7ufkmE6zuq4Eb HcSKNarneHjQ== X-IronPort-AV: E=McAfee;i="6000,8403,9781"; a="185218980" X-IronPort-AV: E=Sophos;i="5.77,404,1596524400"; d="scan'208";a="185218980" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Oct 2020 07:59:53 -0700 IronPort-SDR: lr5HVOpOxoFB8OaszM85N9GhISm0scuKlVva9dKmh67nvDIDhx28uBJIcUMIbSRwkt4GuDKO1J 1nE/0WVj3Eww== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,404,1596524400"; d="scan'208";a="533997448" Received: from silpixa00399126.ir.intel.com ([10.237.222.4]) by orsmga005.jf.intel.com with ESMTP; 22 Oct 2020 07:59:52 -0700 From: Bruce Richardson To: dev@dpdk.org Cc: Bruce Richardson Date: Thu, 22 Oct 2020 15:59:41 +0100 Message-Id: <20201022145944.470054-1-bruce.richardson@intel.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [RFC PATCH 0/3] add custom logging to DPDK meson runs 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" While the meson.log file in each build directory contains lots of information, much of it is not of interest to developers, and it can be hard to see the explicitly messages from the dpdk build files among all the rest of the content. Futhermore, while at the end of the a configuration run we print out the list of enable/disabled components, this is never recorded anywhere for anyone who wants to check that build configuration later. This patchset attempts to solve these issues by supporting a dpdk-meson.log file in each DPDK build folder containing the output from the DPDK meson.build files - including the final summary information for later checking. Bruce Richardson (3): build: add a dpdk-specific meson log file build: shorten top-level build file build: write messages to dpdk build log file app/test/meson.build | 2 +- buildtools/meson.build | 1 + buildtools/write-log-entry.py | 23 +++++++++++++++++++++++ config/arm/meson.build | 2 ++ config/meson.build | 18 ++++++++++++++++++ config/x86/meson.build | 2 ++ drivers/meson.build | 8 +++++--- examples/meson.build | 1 + lib/meson.build | 8 +++++--- meson.build | 31 ++++++++++++------------------- 10 files changed, 70 insertions(+), 26 deletions(-) create mode 100644 buildtools/write-log-entry.py -- 2.25.1