From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 71D6EA0C41; Wed, 15 Sep 2021 18:23:32 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E29AC4068F; Wed, 15 Sep 2021 18:23:31 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mails.dpdk.org (Postfix) with ESMTP id 7FCFD4014F for ; Wed, 15 Sep 2021 18:23:30 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10108"; a="222409282" X-IronPort-AV: E=Sophos;i="5.85,295,1624345200"; d="scan'208";a="222409282" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Sep 2021 09:23:29 -0700 X-IronPort-AV: E=Sophos;i="5.85,295,1624345200"; d="scan'208";a="700284974" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.4.169]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 15 Sep 2021 09:23:28 -0700 Date: Wed, 15 Sep 2021 17:23:24 +0100 From: Bruce Richardson To: dev@dpdk.org Message-ID: References: <20201022145944.470054-1-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201022145944.470054-1-bruce.richardson@intel.com> Subject: Re: [dpdk-dev] [RFC PATCH 0/3] add custom logging to DPDK meson runs X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" On Thu, Oct 22, 2020 at 03:59:41PM +0100, Bruce Richardson wrote: > 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 > Ping on this old RFC set. >From lack of interest, I'd suggest we drop this set from patchwork as "Rejected", but if others do thing it's worth pursuing I can investigate doing a v2, to update to latest codebase. /Bruce