On Thu, Nov 28, 2019 at 12:01 AM Thomas Monjalon wrote:
>
> From: Bruce Richardson
>
> 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 pa
28/11/2019 12:47, Trahe, Fiona:
> HI Bruce, Thomas,
> Doesn't the RTE_OUTPUT environment var already resolve this issue?
RTE_OUTPUT is for the build directory, yes.
This patch is about having a top-level directory for all builds
done by the build test scripts.
ch...@redhat.com; Yigit, Ferruh ;
> dev@dpdk.org; Richardson,
> Bruce
> Subject: [dpdk-dev] [PATCH v2] devtools: control location of test builds
>
> From: Bruce Richardson
>
> By default, both test-build.sh and test-meson-builds.sh scripts create the
> builds they generate
On Thu, Nov 28, 2019 at 12:00:55AM +0100, Thomas Monjalon wrote:
> From: Bruce Richardson
>
> 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 tes
From: Bruce Richardson
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_
5 matches
Mail list logo
