aboutsummaryrefslogtreecommitdiff
path: root/utils
diff options
context:
space:
mode:
authorGravatar Adam Duskett <Aduskett@gmail.com>2019-01-02 10:49:20 -0500
committerGravatar Thomas Petazzoni <thomas.petazzoni@bootlin.com>2019-01-03 11:41:26 +0100
commitbbf32a77ec5883aef5e954379591504ae20e946b (patch)
tree89eecda1067568d2ff062f0c1d61acba34a42cfa /utils
parent5bbc4724633d1d6e04385ccd41db0b77252bdcf8 (diff)
downloadbuildroot-bbf32a77ec5883aef5e954379591504ae20e946b.tar.gz
buildroot-bbf32a77ec5883aef5e954379591504ae20e946b.tar.bz2
utils/test-pkg: force checking dependencies
Currently, if a user runs "make" while specifying a specific package (IE: make -p foo), the Makefile logic skips checking to see if all the dependencies are selected in the specified packages config file. This behavior is useful to test simple packages which do not have "complex" dependencies. However; if a developer uses test-pkg -p ${package_name} to check their package, the package may pass all the checks, but would have otherwise failed with a simple "make" because the developer may have failed to add a select line in packages config file, even if there is a new dependency in the packages Makefile. Pass the environment variable "BR_FORCE_CHECK_DEPENDENCIES" to the Makefile in the test-pkg script, and check it's value in the Makefile. If the value is "YES" force checking for dependency issues. Signed-off-by: Adam Duskett <Aduskett@gmail.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Diffstat (limited to 'utils')
-rwxr-xr-xutils/test-pkg2
1 files changed, 1 insertions, 1 deletions
diff --git a/utils/test-pkg b/utils/test-pkg
index e4f68ed061..1995fa8578 100755
--- a/utils/test-pkg
+++ b/utils/test-pkg
@@ -152,7 +152,7 @@ build_one() {
fi
# shellcheck disable=SC2086
- if ! make O="${dir}" ${pkg} >> "${dir}/logfile" 2>&1; then
+ if ! BR_FORCE_CHECK_DEPENDENCIES=YES make O="${dir}" ${pkg} >> "${dir}/logfile" 2>&1; then
return 2
fi