linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 5/7] kernel-shark-qt: Add a README file to trace-cmd/kernel-shark-qt
Date: Tue, 26 Jun 2018 17:51:07 +0300	[thread overview]
Message-ID: <d336e69a-0e95-4cba-d8a5-0756a150b2c2@gmail.com> (raw)
In-Reply-To: <20180625143810.6c1c5189@gandalf.local.home>



On 25.06.2018 21:38, Steven Rostedt wrote:
> On Mon, 25 Jun 2018 18:01:19 +0300
> "Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:
> 
>> +++ b/kernel-shark-qt/README
>> @@ -0,0 +1,37 @@
>> +
>> +This directory contains the new Qt-based version of the KernelShark GUI.
>> +
>> +
>> +Third Party Software:
>> +------------------------------------------------------------
>> +The external dependencies:
>> +1. In order to install the packages on Ubuntu do the following:
>> +    sudo apt-get install build-essential git cmake -y
>> +
>> +2. In order to install the packages on Fedora, as root do the following:
>> +    dnf install gcc gcc-c++ git cmake -y
> 
> I'm not so sure how useful this "third party software" section is. I
> think it's pretty obvious that gcc, c++ and cmake will be needed.
> 

I would like to have here instructions how to build the code on a 
default out-of-the-box installation of Ubuntu or Fedora. I agree that it 
doesn't make sense as it is right now, but it will start making sense 
when we start adding more and more dependencies.

> 
>> +
>> +
>> +Building:
>> +------------------------------------------------------------
>> +1. Follow the instructions given in trace-cmd/README and build
>> +the original trace-cmd end traceevent libraries.
>> +
>> +2. Do:
>> +    cd kernel-shark-qt/build
>> +    cmake ../
>> +    make
>> +
>> +2.1 In order to create a Doxygen documentation add -D_DOXYGEN_DOC=1
>> +as a CMake Command-Line option.
>> +    cd kernel-shark-qt/build
>> +    cmake -D_DOXYGEN_DOC=1 ../
>> +    make
>> +
>> +2.2.1 Use "make clean" if you want to delete all already compiled object.
>> +
>> +2.2.2 Use the script "cmake_clean.sh" if you want to delete all already
>> +compiled object and all files generated by CMake.
>> +
>> +3. After building the code "kernel-shark-qt/lib" will contain all libraries
>> +and "kernel-shark-qt/bin" will contain all executables.
> 
> Note, after all the code is in the repo, I expect to have the top level
> Makefile, do all the cmake work for the user.
> 

Do you mean, you want to completely remove this README file?

Thanks!
Yordan


> -- Steve
> 

  reply	other threads:[~2018-06-26 14:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 15:01 [PATCH 0/7] Introduce the very basic part of the C API of KS-1.0 Yordan Karadzhov (VMware)
2018-06-25 15:01 ` [PATCH 1/7] kernel-shark-qt: Add Cmake build system for the Qt based KernelShark Yordan Karadzhov (VMware)
2018-06-25 16:06   ` Steven Rostedt
2018-06-26 14:23     ` Yordan Karadzhov (VMware)
2018-06-25 15:01 ` [PATCH 3/7] kernel-shark-qt: Add API for loading trace.dat files Yordan Karadzhov (VMware)
2018-06-25 18:30   ` Steven Rostedt
2018-06-26 14:47     ` Yordan Karadzhov (VMware)
2018-06-26 15:16       ` Steven Rostedt
2018-06-26 15:26         ` Yordan Karadzhov (VMware)
2018-06-25 15:01 ` [PATCH 4/7] kernel-shark-qt: Add an example showing how to load trace data Yordan Karadzhov (VMware)
2018-06-25 18:34   ` Steven Rostedt
2018-06-25 15:01 ` [PATCH 5/7] kernel-shark-qt: Add a README file to trace-cmd/kernel-shark-qt Yordan Karadzhov (VMware)
2018-06-25 18:38   ` Steven Rostedt
2018-06-26 14:51     ` Yordan Karadzhov (VMware) [this message]
2018-06-26 15:18       ` Steven Rostedt
2018-06-25 15:01 ` [PATCH 6/7] kernel-shark-qt: Add filtering to the C API of KernelShark Yordan Karadzhov (VMware)
2018-06-25 19:07   ` Steven Rostedt
2018-06-25 15:01 ` [PATCH 7/7] kernel-shark-qt: Add an example showing how to filter trace data Yordan Karadzhov (VMware)
     [not found] ` <20180625150121.14291-3-y.karadz@gmail.com>
2018-06-25 16:09   ` [PATCH 2/7] kernel-shark-qt: Automatic generation of doxygen documentation Steven Rostedt
2018-06-26 14:29     ` Yordan Karadzhov (VMware)
2018-06-26 15:00       ` Steven Rostedt

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=d336e69a-0e95-4cba-d8a5-0756a150b2c2@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).