From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] devtools/test-meson-builds: reduce output size
Date: Sat, 29 Nov 2025 22:19:10 +0100 [thread overview]
Message-ID: <3862442.irdbgypaU6@thomas> (raw)
In-Reply-To: <20251020155536.1965938-1-bruce.richardson@intel.com>
20/10/2025 17:55, Bruce Richardson:
> The various builds done by the "test-meson-builds.sh" script can take a
> large amount of space on disk. Some simple changes allow us to reduce
> the space used significantly. Specifically:
> * use the default "release" build, which does not include debug
> information, for builds where we won't check ABI.
> * use shared linkage rather than static for the 32-bit builds.
>
> After making these changes a set of builds produced by test-meson-builds
> shrank from ~17G to ~7G on my system.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
I agree with this change. I had done something similar 4 years ago:
https://patches.dpdk.org/project/dpdk/patch/20210808125139.3573701-6-thomas@monjalon.net/
My patch was also adding build types "debug" and "minsize".
Now that clang is fixed, I will work on it (requires fixes for minsize).
Your patch shrinks the build directory from 20G to 9G in my setup.
[...]
> - config $srcdir $builds_dir/$targetdir $cross --werror $*
> + config $srcdir $builds_dir/$targetdir $abicheck $cross --werror $*
There is another call to the function config() for the ABI ref build
which requires to add the new ABI parameter:
- config $abirefdir/src $abirefdir/build $cross \
+ config $abirefdir/src $abirefdir/build ABI $cross \
-Dexamples= $*
compile $abirefdir/build
Applied with this change, thanks.
prev parent reply other threads:[~2025-11-29 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 15:55 Bruce Richardson
2025-10-22 17:28 ` Patrick Robb
2025-11-29 21:19 ` Thomas Monjalon [this message]
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=3862442.irdbgypaU6@thomas \
--to=thomas@monjalon.net \
--cc=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).