add quick start in README

[lttv.git] / ltt / branches / poly / README

diff --git a/ltt/branches/poly/README b/ltt/branches/poly/README
index d1e6a82bee83580a36133cf8752142688c9d6ae4..61aa7ca0442063454037af091a6689d4d1ee0e95 100644 (file)
--- a/ltt/branches/poly/README
+++ b/ltt/branches/poly/README
@@ -9,10 +9,10 @@ see doc/developer/index.html
 
 Some development libraries are needed for compiling :
 
 
 Some development libraries are needed for compiling :
 

-gtk 2 development libraries (libgtk2.0-dev)
-glib 2 development libraries (libglib2.0-dev)
-libpopt development libraries (libpopt-dev)
-libpango development libraries (libpango-dev)
+gtk 2 development libraries (libgtk2.0, libgtk2.0-dev)
+glib 2 development libraries (libglib2.0-0, libglib2.0-dev)
+libpopt development libraries (libpopt0, libpopt-dev)
+libpango development libraries (libpango1.0, libpango1.0-dev)

 
 To compile the source tree from a tarball, simply follow these steps :
 
 
 To compile the source tree from a tarball, simply follow these steps :
 


@@ -24,6 +24,13 @@ After running ./configure, you can also go in specific subdirectories and
 use make, make install.
 
 
 use make, make install.
 
 

+* Quick Start
+
+- Create a trace
+- Convert it
+- Run ./lttv -m guievents -m guicontrolflow -m guievents -t path_to_trace
+
+

 * Source Tree Structure
 
 This is a sample of the suggested tree for Linux Trace Toolkit.
 * Source Tree Structure
 
 This is a sample of the suggested tree for Linux Trace Toolkit.


@@ -41,6 +48,18 @@ lttv/modules:  Linux Trace Toolkit analysis tool and viewer plugin modules.
 specs:  RPM config files (currently empty).
 
 
 specs:  RPM config files (currently empty).
 
 

+* The rest of the tools
+
+You must use the lastest versions of patches for the Linux Kernel. That includes
+relayfs and ltt patches, available on the ltt-dev mailing list at
+http://www.listserv.shafik.org/pipermail/ltt-dev/. You will find there the
+lastest version of the trace daemon that must be used to create the traces. (in
+the TraceToolkit package)
+
+Once your traces are created, you must use the convert tool to create a trace in
+the proper format from them.
+
+

 * For Developers
 
 This source tree is based on the autotools suite from GNU to simplify
 * For Developers
 
 This source tree is based on the autotools suite from GNU to simplify


@@ -57,4 +76,5 @@ If you get the tree from the repository, you will need to use the autogen.sh
 script. It calls all the GNU tools needed to prepare the tree configuration.
 
 
 script. It calls all the GNU tools needed to prepare the tree configuration.
 
 

+

 Mathieu Desnoyers 
 Mathieu Desnoyers