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 99903A3295 for ; Wed, 23 Oct 2019 17:12:38 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D00611C2F8; Wed, 23 Oct 2019 17:12:37 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 38A0A1C2F3 for ; Wed, 23 Oct 2019 17:12:35 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Oct 2019 08:12:35 -0700 X-IronPort-AV: E=Sophos;i="5.68,221,1569308400"; d="scan'208";a="191859945" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.95]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Oct 2019 08:12:33 -0700 Date: Wed, 23 Oct 2019 16:12:30 +0100 From: Bruce Richardson To: Thomas Monjalon Cc: dev@dpdk.org, "Burakov, Anatoly" Message-ID: <20191023151230.GA1735@bricha3-MOBL.ger.corp.intel.com> References: <20190919150755.28018-1-bruce.richardson@intel.com> <364d7c84-9fbd-32fb-5204-abf3733c5386@intel.com> <2151079.TrWVs4AE6D@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2151079.TrWVs4AE6D@xps> User-Agent: Mutt/1.12.1 (2019-06-15) Subject: Re: [dpdk-dev] [PATCH] build: print out dependency names for clarity 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" On Wed, Oct 23, 2019 at 04:40:28PM +0200, Thomas Monjalon wrote: > 18/10/2019 18:54, Burakov, Anatoly: > > On 19-Sep-19 4:07 PM, Bruce Richardson wrote: > > > To help developers to get the correct dependency name e.g. when creating a > > > new example that depends on a specific component, print out the dependency > > > name for each lib/driver as it is processed. > > > > > > Signed-off-by: Bruce Richardson > > > --- > > > > Very nice change, +1! > > > > Tested-by: Anatoly Burakov > > Applied, thanks > > It makes meson processing very verbose. > Is there way to filter meson messages? > Well, we can look to make it build configurable, or only add them for particular build types. However, I think for developers the info it provides is really useful, so I'd like to keep it on by default initially anyway. A good feature to add in 20.02 might be to have settings like this controlled as in make - where we check for the presence of a .git folder, for example. /Bruce