On Wed, Oct 30, 2024 at 05:16:01PM +0000, Bruce Richardson wrote:
> The configuration run of meson produces a lot of output. When running
> test-meson-builds script, or any other script which does multiple
> builds, it can be useful to see the directory in which ninja is being
> run. Currently this requires scrolling back to the top of the output, so
> to simplify things print out the source and build directories at the end
> of the config run, so they are on-screen while ninja is printing its
> output immediately underneath.
>
> Signed-off-by: Bruce Richardson <bruce.richard...@intel.com>
Ping for feedback on this minor patch. It "scratches and itch" for me in my
build testing anyway...
Thanks,
/Bruce
> ---
> meson.build | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/meson.build b/meson.build
> index c59ab7430a..8436d1dff8 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -179,3 +179,7 @@ foreach drv:dpdk_drvs_disabled
> output_message += drv + ':\t' + reason + '\n\t'
> endforeach
> message(output_message + '\n')
> +
> +message('DPDK build config complete:\n' +
> + ' source path = "' + dpdk_source_root + '"\n' +
> + ' build path = "' + dpdk_build_root + '"')
> --
> 2.43.0
>
