[dpdk-dev] [PATCH v2] devtools: control location of test builds

[Bruce Richardson]

On Thu, Nov 28, 2019 at 12:00:55AM +0100, Thomas Monjalon wrote:
> From: Bruce Richardson <bruce.richardson at 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 at intel.com>
> Signed-off-by: Thomas Monjalon <thomas at monjalon.net>
> ---
> v2:
> - rename DPDK_TEST_BUILD_DIR to DPDK_BUILD_TEST_DIR
> - add comment in devtools/test-build.sh and its guide section
> - load from config file in test-meson-builds.sh
> ---

Thanks for the update, those seem ok changes to me. The doc one I should
have caught in the V1, so it's especially welcome.

/Bruce