diff mbox series

build: output source and build dirs at end of config

Message ID 20241030171601.3656819-1-bruce.richardson@intel.com (mailing list archive)
State Accepted, archived
Delegated to: Thomas Monjalon
Headers
Series build: output source and build dirs at end of config |

Checks

Context Check Description
ci/checkpatch success coding style OK
ci/loongarch-compilation success Compilation OK
ci/loongarch-unit-testing success Unit Testing PASS
ci/Intel-compilation success Compilation OK
ci/intel-Testing success Testing PASS
ci/github-robot: build success github build: passed
ci/intel-Functional success Functional PASS
ci/iol-mellanox-Performance success Performance Testing PASS
ci/iol-marvell-Functional success Functional Testing PASS
ci/iol-intel-Functional success Functional Testing PASS
ci/iol-unit-arm64-testing success Testing PASS
ci/iol-broadcom-Performance success Performance Testing PASS
ci/iol-compile-arm64-testing success Testing PASS
ci/iol-unit-amd64-testing success Testing PASS
ci/iol-compile-amd64-testing success Testing PASS
ci/iol-sample-apps-testing success Testing PASS

Commit Message

Bruce Richardson Oct. 30, 2024, 5:16 p.m. UTC 
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>
---
 meson.build | 4 ++++
 1 file changed, 4 insertions(+)

Comments

Bruce Richardson Nov. 19, 2024, 12:08 p.m. UTC | #1 
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
>
Thomas Monjalon Nov. 19, 2024, 3:15 p.m. UTC | #2 
19/11/2024 13:08, Bruce Richardson:
> 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...

Me too.

Applied, thanks.
diff mbox series

Patch

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 + '"')