From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 2/4] trace-cmd: Correct the install paths of traceevent and trace-cmd libraries
Date: Fri, 20 Sep 2019 15:00:26 +0300 [thread overview]
Message-ID: <9fc6f4ba-3095-1022-c13a-8a5df5ec3f0a@gmail.com> (raw)
In-Reply-To: <20190920104831.23475-3-y.karadz@gmail.com>
This one is wrong. Please ignore it.
I am sending v2.
Thanks!
Yordan
On 20.09.19 г. 13:48 ч., Yordan Karadzhov (VMware) wrote:
> In order to be able to use the installed versions of the library's headers
> (and the libraries itself) the directories structure of the source has to
> be reprodused in the install location.
>
> This modification is needed by the NumPy interface of KernelShark.
>
> Signed-off-by: Yordan Karadzhov (VMware) <y.karadz@gmail.com>
> ---
> Makefile | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index dabdf8d..7124b2f 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -344,12 +344,12 @@ install_gui: install_cmd gui
> $(Q)$(MAKE) $(S) -C $(kshark-dir)/build install
>
> install_libs: libs
> - $(Q)$(call do_install,$(LIBTRACECMD_SHARED),$(libdir_SQ))
> - $(Q)$(call do_install,$(LIBTRACEEVENT_SHARED),$(libdir_SQ))
> + $(Q)$(call do_install,$(LIBTRACECMD_SHARED),$(libdir_SQ)/trace-cmd)
> + $(Q)$(call do_install,$(LIBTRACEEVENT_SHARED),$(libdir_SQ)/traceevent)
> $(Q)$(call do_install,$(src)/include/traceevent/event-parse.h,$(includedir_SQ)/traceevent)
> $(Q)$(call do_install,$(src)/include/traceevent/trace-seq.h,$(includedir_SQ)/traceevent)
> - $(Q)$(call do_install,$(src)/include/trace-cmd/trace-cmd.h,$(includedir_SQ))
> - $(Q)$(call do_install,$(src)/include/trace-cmd/trace-filter-hash.h,$(includedir_SQ))
> + $(Q)$(call do_install,$(src)/include/trace-cmd/trace-cmd.h,$(includedir_SQ)/trace-cmd)
> + $(Q)$(call do_install,$(src)/include/trace-cmd/trace-filter-hash.h,$(includedir_SQ)/trace-cmd)
>
> doc:
> $(MAKE) -C $(src)/Documentation all
>
next prev parent reply other threads:[~2019-09-20 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 10:48 [PATCH 0/4] Fixes needed for KS 1.1 Yordan Karadzhov (VMware)
2019-09-20 10:48 ` [PATCH 1/4] kernel-shark: Use correct order when linking all depenancies Yordan Karadzhov (VMware)
2019-09-20 10:48 ` [PATCH 2/4] trace-cmd: Correct the install paths of traceevent and trace-cmd libraries Yordan Karadzhov (VMware)
2019-09-20 12:00 ` Yordan Karadzhov (VMware) [this message]
2019-09-20 10:48 ` [PATCH 3/4] kernel-shark: Fix the file paths used by Doxygen Yordan Karadzhov (VMware)
2019-09-20 10:48 ` [PATCH 4/4] kernel-shark: Cleanup in KsCaptureDialog Yordan Karadzhov (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=9fc6f4ba-3095-1022-c13a-8a5df5ec3f0a@gmail.com \
--to=y.karadz@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).