From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] babeltrace: Integrated from version 0.8
Date: Thu, 12 Jan 2012 14:06:36 -0800 [thread overview]
Message-ID: <4F0F596C.8080806@linux.intel.com> (raw)
In-Reply-To: <7e296b4784e2043a1be8b47cd935bb3e06db1b12.1326337436.git.zumeng.chen@windriver.com>
On 01/11/2012 07:11 PM, Zumeng Chen wrote:
> It provides trace read and write libraries, as well as a trace converter.
>
> Signed-off-by: Zumeng Chen<zumeng.chen@windriver.com>
> ---
> meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb | 28 +++++++++++++++++++++++
> 1 files changed, 28 insertions(+), 0 deletions(-)
> create mode 100644 meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb
>
> diff --git a/meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb b/meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb
> new file mode 100644
> index 0000000..76a76c3
> --- /dev/null
> +++ b/meta/recipes-kernel/lttng-2.0/babeltrace_0.8.bb
> @@ -0,0 +1,28 @@
> +SUMMARY = "Babeltrace - Trace Format Babel Tower"
> +DESCRIPTION = "Babeltrace provides trace read and write libraries in host side, as well as a trace converter, which used to convert LTTng 2.0 traces into human-readable log."
> +HOMEPAGE = "http://www.efficios.com/babeltrace/"
> +BUGTRACKER = "n/a"
> +
> +LICENSE = "MIT& GPLV2"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=8d1a03b3c17bdd158b3cbb34813b1423"
> +
LICENSE vs LIC_FILES_CHKSUM, does the LICENSE file contain both?
also GPLv2 not V2
Sau!
> +inherit autotools
> +
> +DEPENDS = "gtk+ util-linux"
> +
> +SRCREV = "31e670293588d7882a232bc14b93d5e956fa43f4"
> +PV = "0.8+git${SRCPV}"
> +PR = "r0"
> +
> +SRC_URI = "git://git.efficios.com/babeltrace.git;protocol=git"
> +
> +S = "${WORKDIR}/git"
> +
> +do_configure_prepend () {
> + ${S}/bootstrap
> +}
> +
> +# Due to liburcu not building for MIPS currently this recipe needs to
> +# be limited also.
> +# So here let us first suppport x86/arm/powerpc platforms now.
> +COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|powerpc.*)-linux'
next prev parent reply other threads:[~2012-01-12 22:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 3:10 [V4] [PATCH 0/4] lttng-2.0 new recipe for merge Zumeng Chen
2012-01-12 3:11 ` [PATCH 1/4] lttng-ust: Integrate into yocto linux Zumeng Chen
2012-01-12 3:11 ` [PATCH 2/4] lttng-tools: Integrated from git repo Zumeng Chen
2012-01-12 22:04 ` Saul Wold
2012-01-13 0:55 ` zumeng.chen
2012-01-12 3:11 ` [PATCH 3/4] lttng-modules: from lttng-modules 2.0 " Zumeng Chen
2012-01-12 3:11 ` [PATCH 4/4] babeltrace: Integrated from version 0.8 Zumeng Chen
2012-01-12 22:06 ` Saul Wold [this message]
2012-01-13 0:57 ` zumeng.chen
-- strict thread matches above, loose matches on Subject: below --
2012-01-16 16:06 [PATCH 0/4] [V6] lttng-2.0 new recipe Zumeng Chen
2012-01-16 16:06 ` [PATCH 4/4] babeltrace: Integrated from version 0.8 Zumeng Chen
2012-01-13 1:44 [PATCH 0/4] [V5] lttng-2.0 new recipe Zumeng Chen
2012-01-13 1:44 ` [PATCH 4/4] babeltrace: Integrated from version 0.8 Zumeng Chen
[not found] <cover.1326244852.git.zumeng.chen@windriver.com>
2012-01-11 1:31 ` Zumeng Chen
[not found] <cover.1326210673.git.zumeng.chen@windriver.com>
2012-01-10 16:11 ` Zumeng Chen
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=4F0F596C.8080806@linux.intel.com \
--to=sgw@linux.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