X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=ltt%2Fbranches%2Fpoly%2FREADME;h=f8491f6fc61b634c3923e7a8e82c5b3720d27c77;hb=703b25fad5513ff1d7dc442c0e5d278160964f44;hp=3d02eba6f3bdedfce7a7fcd330b07110dc091091;hpb=3e177b6ee783950a3904355feef6046f29b4b042;p=lttv.git

diff --git a/ltt/branches/poly/README b/ltt/branches/poly/README
index 3d02eba6..f8491f6f 100644
--- a/ltt/branches/poly/README
+++ b/ltt/branches/poly/README
@@ -7,6 +7,8 @@ see doc/developer/index.html
 
 * Compiling
 
+gcc 3.2 or higher
+
 Some development libraries are needed for compiling :
 
 gtk 2 development libraries (libgtk2.0, libgtk2.0-dev)
@@ -24,6 +26,13 @@ After running ./configure, you can also go in specific subdirectories and
 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.
@@ -41,6 +50,18 @@ lttv/modules:  Linux Trace Toolkit analysis tool and viewer plugin modules.
 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
@@ -57,4 +78,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.
 
 
+
 Mathieu Desnoyers