From: Bruce Richardson <bruce.richardson@intel.com>
To: <dev@dpdk.org>
Subject: Re: [PATCH] build: output source and build dirs at end of config
Date: Tue, 19 Nov 2024 12:08:58 +0000 [thread overview]
Message-ID: <Zzx_2mBo6gOlNXIO@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20241030171601.3656819-1-bruce.richardson@intel.com>
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.richardson@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
>
next prev parent reply other threads:[~2024-11-19 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 17:16 Bruce Richardson
2024-11-19 12:08 ` Bruce Richardson [this message]
2024-11-19 15:15 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zzx_2mBo6gOlNXIO@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).