X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=ltt%2Fbranches%2Fpoly%2FREADME;h=f8491f6fc61b634c3923e7a8e82c5b3720d27c77;hb=1500e1512ad61fe65ada227dfc6282b5e5f104f3;hp=3effc741728c7bb5ef424d70b7cae66ea2da3f9b;hpb=e8ac6a5ee4cbe4ac130fe2e26f80ca97175b1528;p=lttv.git

diff --git a/ltt/branches/poly/README b/ltt/branches/poly/README
index 3effc741..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.
@@ -40,6 +49,7 @@ lttv:   Linux Trace Toolkit trace analysis tool and viewer.
 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
@@ -51,6 +61,7 @@ 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