linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vladislav Valtchev (VMware)" <vladislav.valtchev@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org,
	"Vladislav Valtchev (VMware)" <vladislav.valtchev@gmail.com>
Subject: [PATCH 0/6] trace-cmd: Make out-of-tree builds to work
Date: Wed, 10 Jan 2018 17:58:26 +0200	[thread overview]
Message-ID: <20180110155832.15928-1-vladislav.valtchev@gmail.com> (raw)

This small series makes out-of-tree builds to work. In order to do that, it's
enough to set the 'O' variable while calling make like: make -O=build_dir.

NOTE[1]: this series has to be applied after the series called:
"trace-cmd: restructure the project's source tree"

Vladislav Valtchev (VMware) (6):
  trace-cmd: Make libtraceevent builable out-of-tree
  trace-cmd: Make the plugins buildable out-of-tree
  trace-cmd: Make libtracecmd buildable out-of-tree
  trace-cmd: Make the trace-cmd target buildable out-of-tree
  trace-cmd: Make the python targets buildable out-of-tree
  trace-cmd: Make the GUI targets buildable out-of-tree

 Makefile                | 57 ++++++++++++++++++++++---------------------------
 kernel-shark/Makefile   | 40 ++++++++++++++++++++++------------
 lib/trace-cmd/Makefile  | 27 +++++++++++++++--------
 lib/traceevent/Makefile | 25 +++++++++++++++-------
 plugins/Makefile        | 37 +++++++++++++++++++-------------
 python/Makefile         | 30 +++++++++++++++-----------
 scripts/utils.mk        |  2 +-
 tracecmd/Makefile       | 33 ++++++++++++++++++----------
 8 files changed, 148 insertions(+), 103 deletions(-)

-- 
2.14.1

             reply	other threads:[~2018-01-10 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 15:58 Vladislav Valtchev (VMware) [this message]
2018-01-10 15:58 ` [PATCH 1/6] trace-cmd: Make libtraceevent builable out-of-tree Vladislav Valtchev (VMware)
2018-01-10 15:58 ` [PATCH 2/6] trace-cmd: Make the plugins buildable out-of-tree Vladislav Valtchev (VMware)
2018-01-10 15:58 ` [PATCH 3/6] trace-cmd: Make libtracecmd " Vladislav Valtchev (VMware)
2018-01-10 15:58 ` [PATCH 4/6] trace-cmd: Make the trace-cmd target " Vladislav Valtchev (VMware)
2018-01-10 15:58 ` [PATCH 5/6] trace-cmd: Make the python targets " Vladislav Valtchev (VMware)
2018-01-10 15:58 ` [PATCH 6/6] trace-cmd: Make the GUI " Vladislav Valtchev (VMware)

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=20180110155832.15928-1-vladislav.valtchev@gmail.com \
    --to=vladislav.valtchev@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).