README

   1 BabelTrace - Trace Format Babel Tower
   2 Mathieu Desnoyers, EfficiOS Inc.
   3 September 2010
   4
   5 This project provides trace read and write libraries, as well as a trace
   6 converter. A plugin can be created for any trace format to allow its conversion
   7 to/from another trace format.
   8
   9 The main format expected to be converted to/from is the Common Trace
  10 Format (CTF). The latest version of the CTF specification can be found at:
  11
  12   git tree:   git://git.efficios.com/ctf.git
  13   gitweb:     http://git.efficios.com/?p=ctf.git
  14
  15 The CE Workgroup of the Linux Foundation, Ericsson, and EfficiOS have
  16 sponsored this work.
  17
  18
  19 BUILDING
  20 --------
  21
  22         ./bootstrap (skip if using tarball)
  23         ./configure
  24         make
  25         make install
  26         ldconfig
  27
  28
  29 DEPENDENCIES
  30 ------------
  31
  32 To compile Babeltrace, you will need:
  33
  34         gcc 3.2 or better
  35         libc6 development librairies
  36           (Debian : libc6, libc6-dev)
  37           (Fedora : glibc, glibc)
  38         glib 2.22 or better development libraries
  39           (Debian : libglib2.0-0, libglib2.0-dev)
  40           (Fedora : glib2, glib2-devel)
  41         uuid development libraries
  42           (Debian : uuid-dev)
  43           (Fedora : uuid-devel)
  44         libpopt development libraries
  45           (Debian : libpopt-dev)
  46           (Fedora : popt)
  47
  48 For developers using the git tree:
  49
  50 This source tree is based on the autotools suite from GNU to simplify
  51 portability. Here are some things you should have on your system in order to
  52 compile the git repository tree :
  53
  54 - GNU autotools (automake >=1.10, autoconf >=2.50, autoheader >=2.50)
  55   (make sure your system wide "automake" points to a recent version!)
  56 - GNU Libtool
  57   (for more information, go to http://www.gnu.org/software/autoconf/)
  58 - Flex >=2.5.35.
  59 - Bison >=2.4.
  60
  61 If you get the tree from the repository, you will need to use the "bootstrap"
  62 script in the root of the tree. It calls all the GNU tools needed to prepare the
  63 tree configuration.