From: Vadim Kochan <vadim4j@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] utils/test-pkg: Generate package config if it is not specified
Date: Fri, 1 Mar 2019 14:33:42 +0200 [thread overview]
Message-ID: <1551443622-29498-1-git-send-email-email@gmail.com> (raw)
From: Vadim Kochan <vadim4j@gmail.com>
It is possible to generate one-line config for the package just by
normalize it to the form:
BR2_PACKAGE_${pkg_replaced-to_and_uppercase}
it simplifes a bit of testing package where no additional config options
are needed.
Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
---
utils/test-pkg | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/utils/test-pkg b/utils/test-pkg
index 1995fa8..cce4679 100755
--- a/utils/test-pkg
+++ b/utils/test-pkg
@@ -2,12 +2,20 @@
set -e
TOOLCHAINS_CSV='support/config-fragments/autobuild/toolchain-configs.csv'
+TEMP_CONF=""
+
+do_clean() {
+ if [ ! -z "${TEMP_CONF}" ]; then
+ rm -f "${TEMP_CONF}"
+ fi
+}
main() {
local o O opts
local cfg dir pkg random toolchains_dir toolchain all number mode
local ret nb nb_skip nb_fail nb_legal nb_tc build_dir
local -a toolchains
+ local pkg_br_name
o='hac:d:n:p:r:t:'
O='help,config-snippet:build-dir:package:,random:,toolchains-dir:'
@@ -50,8 +58,15 @@ main() {
;;
esac
done
+
+ trap do_clean INT TERM HUP EXIT
+
if [ -z "${cfg}" ]; then
- printf "error: no config snippet specified\n" >&2; exit 1
+ pkg_br_name="${pkg//-/_}"
+ pkg_br_name="BR2_PACKAGE_${pkg_br_name^^}"
+ TEMP_CONF=$(mktemp /tmp/test-${pkg}-config.XXXXXX)
+ echo "${pkg_br_name}=y" > ${TEMP_CONF}
+ cfg="${TEMP_CONF}"
fi
if [ ! -e "${cfg}" ]; then
printf "error: %s: no such file\n" "${cfg}" >&2; exit 1
--
2.7.4
next reply other threads:[~2019-03-01 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 12:33 Vadim Kochan [this message]
2019-03-04 7:34 ` [Buildroot] [PATCH 1/1] utils/test-pkg: Generate package config if it is not specified Arnout Vandecappelle
2019-03-17 9:27 ` Thomas Petazzoni
2019-03-27 9:43 ` Peter Korsgaard
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=1551443622-29498-1-git-send-email-email@gmail.com \
--to=vadim4j@gmail.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox