devtools: control location of test builds
authorBruce Richardson <bruce.richardson@intel.com>
Wed, 27 Nov 2019 23:00:55 +0000 (00:00 +0100)
committerThomas Monjalon <thomas@monjalon.net>
Thu, 28 Nov 2019 21:31:53 +0000 (22:31 +0100)
commitaa75995509302edcc8241781504749ed0664b24f
treea98372608142524cdd03afc8b03153232d7916d2
parentb09afc2ad82647ab4f0edc121e9632cc1906c5bb
devtools: control location of test builds

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>
devtools/test-build.sh
devtools/test-meson-builds.sh
doc/guides/contributing/patches.rst