From: Thomas Devoogdt <thomas@devoogdt.com>
To: buildroot@buildroot.org
Cc: Thomas Devoogdt <thomas.devoogdt@barco.com>
Subject: [Buildroot] [PATCH] utils/test-pkg: allow to override the default build directory with an environment variable
Date: Fri, 19 Sep 2025 13:38:37 +0000 [thread overview]
Message-ID: <20250919133837.7065-1-thomas@devoogdt.com> (raw)
From: Thomas Devoogdt <thomas.devoogdt@barco.com>
Currently, there is one way to override the ${HOME}/br-test-pkg default,
using the --build-dir argument. But when doing frequent test runs, it's
just easier to force it with an environment variable, so add it.
Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
---
utils/test-pkg | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/utils/test-pkg b/utils/test-pkg
index cea7ace7cb..32b2486b61 100755
--- a/utils/test-pkg
+++ b/utils/test-pkg
@@ -89,7 +89,7 @@ main() {
printf "error: %s: no such file\n" "${cfg}" >&2; exit 1
fi
if [ -z "${dir}" ]; then
- dir="${HOME}/br-test-pkg"
+ dir="${BR2_TEST_DIR:-${HOME}/br-test-pkg}"
fi
if [ "${random}" -gt 0 ]; then
@@ -271,7 +271,7 @@ Options:
-d DIR, --build-dir DIR
Do the builds in directory DIR, one sub-dir per toolchain.
- If not specified, defaults to \${HOME}/br-test-pkg
+ If not specified, defaults to \${BR2_TEST_DIR}, or \${HOME}/br-test-pkg.
-p PKG, --package PKG
Test-build the package PKG, by running 'make PKG'; if not specified,
--
2.49.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2025-09-19 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 13:38 Thomas Devoogdt [this message]
2026-02-04 15:19 ` [Buildroot] [PATCH] utils/test-pkg: allow to override the default build directory with an environment variable Romain Naour via buildroot
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=20250919133837.7065-1-thomas@devoogdt.com \
--to=thomas@devoogdt.com \
--cc=buildroot@buildroot.org \
--cc=thomas.devoogdt@barco.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.