From: Aaron Conole <aconole@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, ruifeng.wang@arm.com, thomas@monjalon.net,
david.marchand@redhat.com
Subject: Re: [dpdk-dev] [RFC PATCH] ci: reduce examples built for static builds
Date: Mon, 16 Mar 2020 13:36:40 -0400 [thread overview]
Message-ID: <f7tmu8g6w2f.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <20200316170921.6020-1-bruce.richardson@intel.com> (Bruce Richardson's message of "Mon, 16 Mar 2020 17:09:21 +0000")
Bruce Richardson <bruce.richardson@intel.com> writes:
> Static builds can take a lot of space, so reduce the number of examples
> built when doing those static builds.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
It looks good to me. I'll try a run with Ruifeng's no-huge series and
see if I can trigger errors on my side (and then see what happens with
the cache sizes, too). Might take some time as I adjust some things
here.
> .ci/linux-build.sh | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh
> index d500c4c00..2e0971dee 100755
> --- a/.ci/linux-build.sh
> +++ b/.ci/linux-build.sh
> @@ -42,9 +42,15 @@ if [ "$BUILD_32BIT" = "1" ]; then
> export PKG_CONFIG_LIBDIR="/usr/lib32/pkgconfig"
> fi
>
> +if [ "$DEF_LIB" = "static" ] ; then
> + OPTS="$OPTS -Dexamples=l2fwd,l3fwd"
> +else
> + OPTS="$OPTS -Dexamples=all"
> +fi
> +
> OPTS="$OPTS --default-library=$DEF_LIB"
> OPTS="$OPTS --buildtype=debugoptimized"
> -meson build --werror -Dexamples=all $OPTS
> +meson build --werror $OPTS
> ninja -C build
>
> if [ "$AARCH64" != "1" ]; then
next prev parent reply other threads:[~2020-03-16 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 17:09 Bruce Richardson
2020-03-16 17:36 ` Aaron Conole [this message]
2020-03-17 10:44 ` David Marchand
2020-03-17 12:48 ` Aaron Conole
2020-03-16 18:37 ` Thomas Monjalon
2020-03-18 9:45 ` Bruce Richardson
2020-04-17 21:58 ` 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=f7tmu8g6w2f.fsf@dhcp-25.97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
/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).