From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>, dev <dev@dpdk.org>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] devtools: control location of test builds
Date: Thu, 28 Nov 2019 19:40:22 +0100 [thread overview]
Message-ID: <CAJFAV8zG508_RhVMumLGnZE1UHaEjNCNms+MOvdHCpgzKP+_xw@mail.gmail.com> (raw)
In-Reply-To: <20191127230055.23608-1-thomas@monjalon.net>
On Thu, Nov 28, 2019 at 12:01 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> From: Bruce Richardson <bruce.richardson@intel.com>
>
> By default, both test-build.sh and test-meson-builds.sh scripts create the
> builds they generate in the current working directory, leading to a large
> number of build directories being present when testing patches. This
> patchset modifies both scripts to use a DPDK_BUILD_TEST_DIR environment
> variable to control where the build outputs are put.
>
> For example, doing:
> export DPDK_BUILD_TEST_DIR=__builds
> ./devtools/test-meson-builds.sh && ./devtools/test-build.sh \
> x86_64-native-linux-clang+shared i686-native-linux-gcc
>
> gives a "__builds" directory with 14 meson and 2 make builds (with the
> meson build count depending on compiler availability)
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: David Marchand <david.marchand@redhat.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2019-11-28 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 10:10 [dpdk-dev] [PATCH] " Bruce Richardson
2019-11-27 23:00 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2019-11-28 9:48 ` Bruce Richardson
2019-11-28 11:47 ` Trahe, Fiona
2019-11-28 13:20 ` Thomas Monjalon
2019-11-28 18:40 ` David Marchand [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=CAJFAV8zG508_RhVMumLGnZE1UHaEjNCNms+MOvdHCpgzKP+_xw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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).