X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=ltt%2Fbranches%2Fpoly%2FREADME;h=6cf451f4e4d3bf680e192139f58182c25151470c;hb=a970363f31999693ffbc0d7d6cf8a15d03677d64;hp=f8491f6fc61b634c3923e7a8e82c5b3720d27c77;hpb=8023c35ad0b7cc00348b4d299409a3eaf4bd52eb;p=lttv.git

diff --git a/ltt/branches/poly/README b/ltt/branches/poly/README
index f8491f6f..6cf451f4 100644
--- a/ltt/branches/poly/README
+++ b/ltt/branches/poly/README
@@ -1,24 +1,37 @@
+LTT Viewing Tools package README
+--------------------------------
+Mathieu Desnoyers 
+Last update: 2007/05/14
+
 
 This package contains the trace reading library and trace viewing tools for
-the new Linux Trace Toolkit trace format. The associated kernel files to
-generate the new traces are not yet included. In the meantime, a converter
-from the old trace format to the new is provided. For more detailed information
-see doc/developer/index.html
+the new Linux Trace Toolkit trace format.
 
 * Compiling
 
-gcc 3.2 or higher
-
-Some development libraries are needed for compiling :
+gcc 3.2 or better
+gtk 2.4 or better development libraries
+  (Debian : libgtk2.0, libgtk2.0-dev)
+  (Fedora : gtk2, gtk2-devel)
+  note : For Fedora users : this might require at least core 3 from Fedora,
+  or you might have to compile your own GTK2 library.
+glib 2.4 or better development libraries
+  (Debian : libglib2.0-0, libglib2.0-dev)
+  (Fedora : glib2, glib2-devel)
+libpopt development libraries
+  (Debian : libpopt0, libpopt-dev)
+  (Fedora : popt)
+libpango development libraries
+  (Debian : libpango1.0, libpango1.0-dev)
+  (Fedora : pango, pango-devel)
+libc6 development librairies 
+  (Debian : libc6, libc6-dev)
+  (Fedora : glibc, glibc)
 
-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 :
 
-- run ./configure
+- ./configure
 - make
 - make install
 
@@ -28,38 +41,22 @@ use make, make install.
 
 * Quick Start
 
-- Create a trace
-- Convert it
-- Run ./lttv -m guievents -m guicontrolflow -m guievents -t path_to_trace
+See QUICKSTART.
 
 
 * Source Tree Structure
 
-This is a sample of the suggested tree for Linux Trace Toolkit.
-
-ltt: new trace format reading library (and converter).
-README: This file.
-debian: debian config files (currently empty).
-doc:    Documentation.
-doc/user:      User related documentation.
-doc/developer: Developer related documentation.
-kernel: Linux Trace Toolkit kernel code (currently empty).
-lttd:   Linux Trace Toolkit daemon (currently empty).
-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
+Here is the tree structure of the Linux Trace Toolkit Viewer package.
 
-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.
+ltt/		New trace format reading library.
+README		This file.
+debian/		Debian config files (currently empty).
+doc/		Documentation.
+doc/user/	User related documentation.
+doc/developer/	Developer related documentation.
+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).
 
 
 * For Developers
@@ -69,14 +66,10 @@ portability. Here are some things you should have on your system in order to
 compile the subversion repository tree :
 
 
-GNU autotools (automake-1,7, autoconf2.50, autoheader2.50)
-(make sure your system wide "automake" points to version 1.7!)
-GNU Libtool
-(for more information, go to http://www.gnu.org/software/autoconf/)
+- GNU autotools (automake >=1.7, autoconf >=2.50, autoheader >=2.50)
+  (make sure your system wide "automake" points to a recent version!)
+- GNU Libtool
+  (for more information, go to http://www.gnu.org/software/autoconf/)
 
 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