From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] New: add lava-test package
Date: Fri, 27 Apr 2012 17:12:26 +0200 [thread overview]
Message-ID: <4F9AB75A.8040607@visionsystems.de> (raw)
In-Reply-To: <1335539086-10206-1-git-send-email-ludovic.desroches@atmel.com>
Am 27.04.2012 17:04, schrieb ludovic.desroches at atmel.com:
> From: Ludovic Desroches <ludovic.desroches@atmel.com>
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> ---
> package/Config.in | 1 +
> package/lava-test/Config.in | 8 ++++++++
> package/lava-test/lava-test.mk | 11 +++++++++++
> 3 files changed, 20 insertions(+), 0 deletions(-)
> create mode 100644 package/lava-test/Config.in
> create mode 100644 package/lava-test/lava-test.mk
>
> diff --git a/package/Config.in b/package/Config.in
> index 3e5f708..79f9aaf 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -22,6 +22,7 @@ source "package/dhrystone/Config.in"
> source "package/dstat/Config.in"
> source "package/dmalloc/Config.in"
> source "package/kexec/Config.in"
> +source "package/lava-test/Config.in"
> source "package/lmbench/Config.in"
> source "package/lsof/Config.in"
> source "package/ltp-testsuite/Config.in"
> diff --git a/package/lava-test/Config.in b/package/lava-test/Config.in
> new file mode 100644
> index 0000000..d13dfd7
> --- /dev/null
> +++ b/package/lava-test/Config.in
> @@ -0,0 +1,8 @@
> +config BR2_PACKAGE_LAVA_TEST
> + bool "lava-test"
> + help
> + LAVA Test is a test execution framework designed to make it easy to
> + install and run supported tests. Results from testing can be
> + optionally uploaded to a dashboard running lava-dashboard.
> +
> + https://launchpad.net/lava-test
> diff --git a/package/lava-test/lava-test.mk b/package/lava-test/lava-test.mk
> new file mode 100644
> index 0000000..f6df4a2
> --- /dev/null
> +++ b/package/lava-test/lava-test.mk
> @@ -0,0 +1,11 @@
> +LAVA_TEST_VERSION = 0.7
> +LAVA_TEST_SOURCE = lava-test-$(LAVA_TEST_VERSION)-2012.04.tar.gz
> +LAVA_TEST_SITE = https://launchpad.net/lava-test/trunk/2012.04/+download/
> +LAVA_TEST_DEPENDENCIES = python-setuptools
> +
> +define LAVA_TEST_INSTALL_TARGET_CMDS
> + (cd $(@D); PYTHONPATH="$(TARGET_DIR)/usr/lib/python$(PYTHON_VERSION_MAJOR)/site-packages"\
> + $(HOST_DIR)/usr/bin/python setup.py install --prefix=$(TARGET_DIR)/usr)
> +endef
> +
> +$(eval $(call GENTARGETS))
Thank you for the patch. I'll look at it next week.
Yegor
next prev parent reply other threads:[~2012-04-27 15:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 13:42 [Buildroot] setup.py: issue with python path Ludovic Desroches
2012-04-27 14:30 ` Yegor Yefremov
2012-04-27 15:04 ` [Buildroot] [PATCH] New: add lava-test package ludovic.desroches at atmel.com
2012-04-27 15:12 ` Yegor Yefremov [this message]
2012-04-27 15:35 ` Ludovic Desroches
2012-05-07 14:08 ` Yegor Yefremov
2012-05-10 7:30 ` ludovic.desroches
2012-05-10 7:39 ` Yegor Yefremov
2012-05-14 7:46 ` ludovic.desroches
2012-05-14 7:51 ` Yegor Yefremov
-- strict thread matches above, loose matches on Subject: below --
2013-10-08 15:17 [Buildroot] Buildroot patchwork: decision on the 10 oldest patches, week 1 Ludovic Desroches
2013-10-09 9:34 ` [Buildroot] [PATCH] New: add lava-test package ludovic.desroches at atmel.com
2013-10-09 11:55 ` Thomas Petazzoni
2013-10-09 14:42 ` Ludovic Desroches
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=4F9AB75A.8040607@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--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