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

Thomas Monjalon thomas at monjalon.net
Tue May 19 16:50:56 CEST 2020


07/05/2020 12:13, 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 header files, the meson build
> fails and it can only be fixed by either updating that library, or
> expanding the meson script for the faulty PMD.
> 
> While the latter should be still done for the sake of DPDK quality,
> an intermediate solution would be to skip building the faulty PMD
> - there's a chance we don't need it. That's what this patch allows.
> 
> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk at intel.com>
> Acked-by: Bruce Richardson <bruce.richardson at intel.com>
> ---
> v2:
>  - simplified the code with if X.contains(), as Bruce suggested
>  - removed the related comment from the code - it should be
>    self-documented now

Applied, thanks




More information about the dev mailing list