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

diff --git a/ltt/branches/poly/README b/ltt/branches/poly/README
index 3effc741..6cf451f4 100644
--- a/ltt/branches/poly/README
+++ b/ltt/branches/poly/README
@@ -1,22 +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
 
-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
 
@@ -24,32 +39,25 @@ After running ./configure, you can also go in specific subdirectories and
 use make, make install.
 
 
-* Source Tree Structure
+* Quick Start
 
-This is a sample of the suggested tree for Linux Trace Toolkit.
+See QUICKSTART.
 
-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
+* Source Tree Structure
+
+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)
+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).
 
-Once your traces are created, you must use the convert tool to create a trace in
-the proper format from them.
 
 * For Developers
 
@@ -58,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