From: Philippe Proulx <eeppeliteloop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/7] lttng-babeltrace: update Config.in's help
Date: Fri, 6 Mar 2015 12:35:55 -0500 [thread overview]
Message-ID: <1425663357-22541-6-git-send-email-eeppeliteloop@gmail.com> (raw)
In-Reply-To: <1425663357-22541-1-git-send-email-eeppeliteloop@gmail.com>
Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
---
package/lttng-babeltrace/Config.in | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/package/lttng-babeltrace/Config.in b/package/lttng-babeltrace/Config.in
index 3fe1b3a..c5eb5e0 100644
--- a/package/lttng-babeltrace/Config.in
+++ b/package/lttng-babeltrace/Config.in
@@ -9,12 +9,15 @@ config BR2_PACKAGE_LTTNG_BABELTRACE
depends on BR2_LARGEFILE # util-linux
depends on BR2_UCLIBC_VERSION_SNAPSHOT || BR2_TOOLCHAIN_USES_GLIBC # posix_fallocate
help
- Babeltrace is part of the LTTng 2.x project.
+ The Babeltrace project provides trace read and write libraries,
+ as well as a trace converter application. Plugins can be created
+ for any trace format to allow its conversion to/from another
+ trace format.
- This project provides trace read and write libraries, as
- well as a trace converter. A plugin can be created for any
- trace format to allow its conversion to/from another trace
- format.
+ Babeltrace is the reference implementation of the Common
+ Trace Format (see <http://diamon.org/docs/ctf/>). Babeltrace
+ can decode and display LTTng traces, since the latter
+ are written using the CTF format.
Having this tool on the target is not mandatory. You can
transfer the binary trace output from the target to your
@@ -23,7 +26,7 @@ config BR2_PACKAGE_LTTNG_BABELTRACE
$(O)/host/usr/bin/babeltrace as a dependency of the
lttng-tools package.
- http://lttng.org
+ http://www.efficios.com/babeltrace
comment "lttng-babeltrace needs a uclibc snapshot or (e)glib toolchain w/ wchar, threads, largefile"
depends on BR2_USE_MMU
--
2.2.1
next prev parent reply other threads:[~2015-03-06 17:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 17:35 [Buildroot] [PATCH 0/7] General LTTng packages maintenance Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 1/7] liburcu: bump to version 0.8.6 Philippe Proulx
2015-03-06 22:21 ` Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 2/7] lttng-tools: bump to version 2.6.0 Philippe Proulx
2015-03-06 22:21 ` Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 3/7] lttng-libust: " Philippe Proulx
2015-03-06 22:24 ` Thomas Petazzoni
2015-03-07 0:33 ` Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 4/7] lttng-modules: " Philippe Proulx
2015-03-06 22:28 ` Thomas Petazzoni
2015-03-07 0:35 ` Philippe Proulx
2015-03-06 17:35 ` Philippe Proulx [this message]
2015-03-06 22:30 ` [Buildroot] [PATCH 5/7] lttng-babeltrace: update Config.in's help Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 6/7] lttng-libust: rename package to lttng-ust Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 7/7] lttng-babeltrace: rename package to babeltrace Philippe Proulx
2015-03-06 22:32 ` [Buildroot] [PATCH 0/7] General LTTng packages maintenance Thomas Petazzoni
2015-03-07 1:02 ` Arnout Vandecappelle
2015-03-07 7:59 ` Thomas Petazzoni
2015-03-07 20:50 ` Philippe Proulx
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=1425663357-22541-6-git-send-email-eeppeliteloop@gmail.com \
--to=eeppeliteloop@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