Re: [dpdk-dev] [PATCH] build: don't parse build configs of explicitly disabled drivers

2020-05-07 Thread Stojaczyk, Dariusz
> -Original Message- > From: Bruce Richardson > Sent: Monday, March 30, 2020 3:53 PM > To: Stojaczyk, Dariusz > Cc: dev@dpdk.org > Subject: Re: [PATCH] build: don't parse build configs of explicitly disabled > drivers > > [SNIP] > > Looking at this code and the meson docs again, I thin

Re: [dpdk-dev] [PATCH] build: don't parse build configs of explicitly disabled drivers

2020-03-30 Thread Bruce Richardson
On Thu, Mar 26, 2020 at 10:22:59AM +0100, Darek Stojaczyk wrote: > Even when a PMD was disabled with meson's disable_drivers option > its config file was still being parsed. Some of the PMD configs > attempt to find a library they depend on and parse its header files > with certain assumptions. If

Re: [dpdk-dev] [PATCH] build: don't parse build configs of explicitly disabled drivers

2020-03-26 Thread Bruce Richardson
On Thu, Mar 26, 2020 at 10:22:59AM +0100, Darek Stojaczyk wrote: > Even when a PMD was disabled with meson's disable_drivers option > its config file was still being parsed. Some of the PMD configs > attempt to find a library they depend on and parse its header files > with certain assumptions. If

[dpdk-dev] [PATCH] build: don't parse build configs of explicitly disabled drivers

2020-03-26 Thread Darek Stojaczyk
Even when a PMD was disabled with meson's disable_drivers option its config file was still being parsed. Some of the PMD configs attempt to find a library they depend on and parse its header files with certain assumptions. If the library is found, but it's simply too old to contain the necessary he