Python bindings: add has_intersection property to TraceCollection

[babeltrace.git] / README

diff --git a/README b/README
index 1687075bba2ce9b065d1ce1fec622800dec927af..c44b5e9892a0bd1f71186c6948e44f120378ad20 100644 (file)
--- a/README
+++ b/README
@@ -1,6 +1,4 @@
 BabelTrace - Trace Format Babel Tower
-Mathieu Desnoyers, EfficiOS Inc.
-September 2010
 
 This project provides trace read and write libraries, as well as a trace
 converter. A plugin can be created for any trace format to allow its conversion
@@ -15,6 +13,13 @@ Format (CTF). The latest version of the CTF specification can be found at:
 The CE Workgroup of the Linux Foundation, Ericsson, and EfficiOS have
 sponsored this work.
 
+The current maintainers are:
+  Jérémie Galarneau <jeremie.galarneau@efficios.com>
+  Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
+
+Questions should be addressed to this mailing list:
+  lttng-dev@lists.lttng.org
+
 
 BUILDING
 --------
@@ -25,7 +30,6 @@ BUILDING
        make install
        ldconfig
 
-       If you do not want Python bindings, run ./configure --disable-python.
 
 DEPENDENCIES
 ------------
@@ -45,11 +49,22 @@ To compile Babeltrace, you will need:
        libpopt >= 1.13 development libraries
          (Debian : libpopt-dev)
          (Fedora : popt)
+       elfutils >= 0.154 development libraries (optional)
+         (Debian : libelf-dev, libdw-dev)
+         (Fedora : elfutils-devel, elfutils-libelf-devel)
        python headers (optional)
-         (Debian/Ubuntu : python-dev)
+         (Debian/Ubuntu : python3-dev)
        swig >= 2.0 (optional)
          (Debian/Ubuntu : swig2.0)
+       python 3.0 or better (optional)
+         (Debian/Ubuntu : python3)
 
+  If you want Python bindings, run ./configure --enable-python-bindings.
+  Please note that some distributions will need the following
+  environment variables set before running configure:
+
+    export PYTHON="python3"
+    export PYTHON_CONFIG="/usr/bin/python3-config"
 
 For developers using the git tree:
 
@@ -67,3 +82,5 @@ compile the git repository tree :
 If you get the tree from the repository, you will need to use the "bootstrap"
 script in the root of the tree. It calls all the GNU tools needed to prepare the
 tree configuration.
+
+Running "make check": bash is required.