From: Radu Moisan <radu.moisan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] dbus-tests: Add separate recipe for building dbus-tests
Date: Fri, 17 Aug 2012 16:44:21 +0300 [thread overview]
Message-ID: <502E4AB5.8030206@intel.com> (raw)
In-Reply-To: <fe8f0c9d64b8fb123545d8afcd7891c6d6d90728.1345208249.git.andrei.gherzan@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2428 bytes --]
On 08/17/2012 04:02 PM, Andrei Gherzan wrote:
> While compiling dbus with tests, dbus and dbus-glib are needed.
> To compile dbus-glib, dbus is needed (obviously). The only solution
> (to compile dbus with tests) is to create a new recipe where to
> compile dbus with --enable-tests --enable-embedded-tests, skip write
> to sysroot (noexec) and just package dbus-tests.
> A bash wrapper to run all tests is included.
>
> Signed-off-by: Andrei Gherzan <andrei.gherzan@windriver.com>
> ---
> meta/recipes-core/dbus/dbus-tests/run_test.sh | 22 +++++++++
> meta/recipes-core/dbus/dbus-tests_1.4.20.bb | 64 +++++++++++++++++++++++++
> 2 files changed, 86 insertions(+), 0 deletions(-)
> create mode 100755 meta/recipes-core/dbus/dbus-tests/run_test.sh
> create mode 100644 meta/recipes-core/dbus/dbus-tests_1.4.20.bb
>
> diff --git a/meta/recipes-core/dbus/dbus-tests/run_test.sh b/meta/recipes-core/dbus/dbus-tests/run_test.sh
> new file mode 100755
> index 0000000..90abad2
> --- /dev/null
> +++ b/meta/recipes-core/dbus/dbus-tests/run_test.sh
> @@ -0,0 +1,22 @@
> +#!/bin/sh
> +
> +# Tests location
> +export DBUS_TEST_HOMEDIR=/usr/lib/dbus-tests
> +# Tests data location
> +export DBUS_TEST_DATA=${DBUS_TEST_HOMEDIR}/test/data
> +
> +TESTS=" \
> + bus/bus-test \
> + bus/bus-test-system \
> + dbus/dbus-test \
> + bus/bus-test-launch-helper \
> + test/shell-test \
> + test/test-corrupt \
> + test/test-dbus-daemon \
> + test/test-loopback \
> + test/test-marshal \
> + test/test-relay \
> + test/test-syslog \
> + test/test-refs"
> +
> +${DBUS_TEST_HOMEDIR}/test/dbus-test-runner ${DBUS_TEST_HOMEDIR} ${TESTS}
> diff --git a/meta/recipes-core/dbus/dbus-tests_1.4.20.bb b/meta/recipes-core/dbus/dbus-tests_1.4.20.bb
> new file mode 100644
> index 0000000..0e7d272
> --- /dev/null
> +++ b/meta/recipes-core/dbus/dbus-tests_1.4.20.bb
> @@ -0,0 +1,64 @@
> +FILESEXTRAPATHS_append := "${THISDIR}/dbus-${PV}"
> +include recipes-core/dbus/dbus.inc
> +
> +PR = "${INC_PR}.0"
> +
> +SRC_URI[md5sum] = "79eca2f2c1894ac347acce128314428b"
> +SRC_URI[sha256sum] = "103bdcd261a13140730b5fa69f56a98ab5c89ba3f0116ea62fcfd639520d5aaf"
> +
> +DEPENDS += "python-pygobject-native python-dbus-native dbus-glib dbus"
> +RDEPENDS_${PN} = "dbus-x11"
wouldn't RDEPENDS_${PN} = "dbus" be a better choice since dbus-x11 is
RPROVIDED only for compatibility reasons?
radu
[-- Attachment #2: Type: text/html, Size: 2976 bytes --]
next prev parent reply other threads:[~2012-08-17 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 13:02 [PATCH 0/2] Build and package dbus-tests - separate recipe Andrei Gherzan
2012-08-17 13:02 ` [PATCH 2/2] dbus-tests: Add separate recipe for building dbus-tests Andrei Gherzan
2012-08-17 13:44 ` Radu Moisan [this message]
2012-08-17 13:43 ` Andrei Gherzan
2012-08-17 13:05 ` [PATCH 1/2] python-dbus: Native dbus python module needed for dbus tests Andrei Gherzan
2012-08-17 13:09 ` Martin Jansa
2012-08-17 13:55 ` Andrei Gherzan
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=502E4AB5.8030206@intel.com \
--to=radu.moisan@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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