[dpdk-dev] [PATCH] build: print out dependency names for clarity

Bruce Richardson bruce.richardson at intel.com
Wed Oct 23 17:12:30 CEST 2019


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


More information about the dev mailing list