[PATCH 2/2] build: export dpdk_includes for subproject usage.

[Bruce Richardson]

On Wed, Oct 12, 2022 at 04:47:04PM +0200, Markus Theil wrote:
> From: Thorben Roemer <thorben.roemer at secunet.com>
> 
> In order to perform things like LTO more easily in
> our DPDK applications, we use DPDK as a meson subproject.
> Also export includes in order to be usable in this context.
> 
> Signed-off-by: Thorben Roemer <thorben.roemer at secunet.com>
> ---
>  drivers/meson.build | 1 +
>  lib/meson.build     | 1 +
>  meson.build         | 1 +
>  3 files changed, 3 insertions(+)
> 
> diff --git a/drivers/meson.build b/drivers/meson.build
> index 216971f4e2..d19b47df12 100644
> --- a/drivers/meson.build
> +++ b/drivers/meson.build
> @@ -95,6 +95,7 @@ foreach subpath:subdirs
>          objs = []
>          cflags = default_cflags
>          includes = [include_directories(drv_path)]
> +        dpdk_includes += [include_directories(drv_path)]

I am not sure that by default we should include all the driver directories.
At most, we should only include those drivers which have header files to be
made public. I think initially though we should only export library paths.

/Bruce