All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH] build: print out dependency names for clarity
Date: Wed, 23 Oct 2019 16:12:30 +0100	[thread overview]
Message-ID: <20191023151230.GA1735@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <2151079.TrWVs4AE6D@xps>

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 <bruce.richardson@intel.com>
> > > ---
> > 
> > Very nice change, +1!
> > 
> > Tested-by: Anatoly Burakov <anatoly.burakov@intel.com>
> 
> 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

      reply	other threads:[~2019-10-23 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 15:07 [dpdk-dev] [PATCH] build: print out dependency names for clarity Bruce Richardson
2019-10-18 16:54 ` Burakov, Anatoly
2019-10-23 14:40   ` Thomas Monjalon
2019-10-23 15:12     ` Bruce Richardson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191023151230.GA1735@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.