Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Floury <p.floury@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] trace-cmd : new package
Date: Fri,  2 Aug 2013 14:01:11 +0200	[thread overview]
Message-ID: <1375444871-6771-1-git-send-email-pierre.floury@gmail.com> (raw)

This commit adds a new package for the trace-cmd tool.
This tool is a command line front end of ftrace.
It collects traces on your target.
You can analyse these traces on the target or on the host via
the gui "kernel shark".

http://git.kernel.org/cgit/linux/kernel/git/rostedt/trace-cmd.git

Signed-off-by: Pierre Floury <pierre.floury@gmail.com>

---
Change since v3 :
- apply change recommanded by Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net>
- respect the #80 in the header of the mk file
Change since v2 :
- apply change recommanded by Thomas De Schampheleire
- use full name in signed off
- use alphabetic order on Config.in
- respect the #80

Change since v1 :
- apply change recommanded by Thomas De Schampheleire and Thomas
Petazzoni
- set good license
- set good license files
- change name in the .mk from TRACECMD to TRACE_CMD
- change comment on the Config.in
- use a tag git instread of a commit number

to merge back
---
 package/Config.in              |    1 +
 package/trace-cmd/Config.in    |   10 ++++++++++
 package/trace-cmd/trace-cmd.mk |   23 +++++++++++++++++++++++
 3 files changed, 34 insertions(+)
 create mode 100644 package/trace-cmd/Config.in
 create mode 100644 package/trace-cmd/trace-cmd.mk

diff --git a/package/Config.in b/package/Config.in
index 7069d77..f5b14f6 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -48,6 +48,7 @@ source "package/strace/Config.in"
 source "package/stress/Config.in"
 source "package/sysprof/Config.in"
 source "package/tinymembench/Config.in"
+source "package/trace-cmd/Config.in"
 source "package/whetstone/Config.in"
 source "package/valgrind/Config.in"
 source "package/pv/Config.in"
diff --git a/package/trace-cmd/Config.in b/package/trace-cmd/Config.in
new file mode 100644
index 0000000..5b2b5e4
--- /dev/null
+++ b/package/trace-cmd/Config.in
@@ -0,0 +1,10 @@
+config BR2_PACKAGE_TRACE_CMD
+	bool "trace-cmd"
+	help
+	  Command line reader for ftrace
+	  To use this profiling tool, you should enable ftrace in your kernel
+	  configuration. This command collect traces on your target.
+	  You can analyse these traces on the target or on the host via the gui
+	  "kernel shark"
+
+	  http://git.kernel.org/cgit/linux/kernel/git/rostedt/trace-cmd.git
diff --git a/package/trace-cmd/trace-cmd.mk b/package/trace-cmd/trace-cmd.mk
new file mode 100644
index 0000000..51c9427
--- /dev/null
+++ b/package/trace-cmd/trace-cmd.mk
@@ -0,0 +1,23 @@
+################################################################################
+#
+# trace-cmd
+#
+################################################################################
+
+TRACE_CMD_VERSION = trace-cmd-v2.2.1
+TRACE_CMD_SITE = http://git.kernel.org/cgit/linux/kernel/git/rostedt/trace-cmd.git
+TRACE_CMD_SITE_METHOD = git
+TRACE_CMD_INSTALL_STAGING = YES
+TRACE_CMD_LICENSE = GPLv2 LGPLv2.1
+TRACE_CMD_LICENSE_FILES = COPYING COPYING.LIB
+define TRACE_CMD_BUILD_CMDS
+     $(MAKE) CC="$(TARGET_CC)" LD="$(TARGET_LD)" -C $(@D) all
+endef
+
+define TRACE_CMD_INSTALL_TARGET_CMDS
+	$(INSTALL) -D -m 0755 $(@D)/trace-cmd $(TARGET_DIR)/usr/bin
+	$(INSTALL) -d -m 0755 $(TARGET_DIR)/usr/lib/trace-cmd/plugins
+	$(INSTALL) -D -m 0755 $(@D)/plugin_*.so $(TARGET_DIR)/usr/lib/trace-cmd/plugins
+endef
+
+$(eval $(generic-package))
-- 
1.7.10.4

             reply	other threads:[~2013-08-02 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 12:01 Pierre Floury [this message]
2013-08-02 12:03 ` [Buildroot] [PATCH v4] trace-cmd : new package pierre
2013-08-02 12:20   ` Thomas Petazzoni

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=1375444871-6771-1-git-send-email-pierre.floury@gmail.com \
    --to=p.floury@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