tmf: lttngControl: mi: Component and CreateSession tests

[deliverable/tracecompass.git] / README

diff --git a/README b/README
index 79daa421e8c7045e7869372b62b8867f3defba4c..88ebf2355027c82710e73163d65658f6de40c3cd 100644 (file)
--- a/README
+++ b/README
@@ -6,6 +6,7 @@ org.eclipse.linuxtools.ctf.*          Common Trace Format (CTF) reader library
 org.eclipse.linuxtools.gdbtrace.*     Support for reading and viewing GDB traces
 org.eclipse.linuxtools.lttng2.*       LTTng 2.x integration
 org.eclipse.linuxtools.tmf.*          Tracing and Monitoring Framework
+org.eclipse.linuxtools.statesystem.*  State System library
 org.eclipse.linuxtools.tracing.rcp.*  Code specific to the RCP version
 
 See the plugins.svg file for a diagram showing the dependencies between the
@@ -35,6 +36,7 @@ take some time, to skip them you can append "-Dmaven.test.skip=true" to the
 'mvn' command:
 $ mvn clean install -Dmaven.test.skip=true
 
+
 The RCP is not built by default, to build it you need to add "-PtracingRcp" to
 the 'mvn' command:
 $ mvn clean install -PtracingRcp -Dmaven.test.skip=true
@@ -42,3 +44,15 @@ $ mvn clean install -PtracingRcp -Dmaven.test.skip=true
 This will build the RCP for all supported architectures. The resulting archives
 will be placed in lttng/org.eclipse.linuxtools.tracing.rcp.product/target/products
 
+
+To build a local p2 update site (LTTng integration only)
+$ mvn clean install -PlttngPackage
+
+This will place the p2 update site under the default location
+/var/www/tools/linuxtools/lttng/update-nightly/
+
+To change the package location, use:
+$ mvn clean install -PlttngPackage "-DlttngPackageDestination=<package destination>"
+
+where <package destination> is the absolute path to destination directory on your disk.
+