Fix: Added a null pointer check to bt_ctf_field_name
[babeltrace.git] / README
... / ...
CommitLineData
1BabelTrace - Trace Format Babel Tower
2Mathieu Desnoyers, EfficiOS Inc.
3September 2010
4
5This project provides trace read and write libraries, as well as a trace
6converter. A plugin can be created for any trace format to allow its conversion
7to/from another trace format.
8
9The main format expected to be converted to/from is the Common Trace
10Format (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
15The CE Workgroup of the Linux Foundation, Ericsson, and EfficiOS have
16sponsored this work.
17
18
19BUILDING
20--------
21
22 ./bootstrap (skip if using tarball)
23 ./configure
24 make
25 make install
26 ldconfig
27
28 If you do not want Python bindings, run ./configure --disable-python.
29
30DEPENDENCIES
31------------
32
33To compile Babeltrace, you will need:
34
35 gcc 3.2 or better
36 libc6 development librairies
37 (Debian : libc6, libc6-dev)
38 (Fedora : glibc, glibc)
39 glib 2.22 or better development libraries
40 (Debian : libglib2.0-0, libglib2.0-dev)
41 (Fedora : glib2, glib2-devel)
42 uuid development libraries
43 (Debian : uuid-dev)
44 (Fedora : uuid-devel)
45 libpopt >= 1.13 development libraries
46 (Debian : libpopt-dev)
47 (Fedora : popt)
48 python headers (optional)
49 (Debian/Ubuntu : python-dev)
50 swig >= 2.0 (optional)
51 (Debian/Ubuntu : swig2.0)
52
53
54For developers using the git tree:
55
56This source tree is based on the autotools suite from GNU to simplify
57portability. Here are some things you should have on your system in order to
58compile the git repository tree :
59
60- GNU autotools (automake >=1.10, autoconf >=2.50, autoheader >=2.50)
61 (make sure your system wide "automake" points to a recent version!)
62- GNU Libtool >=2.2
63 (for more information, go to http://www.gnu.org/software/autoconf/)
64- Flex >=2.5.35.
65- Bison >=2.4.
66
67If you get the tree from the repository, you will need to use the "bootstrap"
68script in the root of the tree. It calls all the GNU tools needed to prepare the
69tree configuration.
70
71Running "make check": bash is required.
This page took 0.02177 seconds and 4 git commands to generate.