| commit | 6f8c82b769a6013f302d1237aab5402221830f60 | [log] [tgz] |
|---|---|---|
| author | Marc-Andre Laperle <marc-andre.laperle@ericsson.com> | Fri Jun 26 00:44:12 2015 -0400 |
| committer | Marc-Andre Laperle <marc-andre.laperle@ericsson.com> | Mon Jun 29 17:59:04 2015 -0400 |
| tree | 52ecdfd3a057fd0aa994da792acf4e2ec56f3cf7 | |
| parent | f54c35dcdfb60d8cad90016c8814e98e7b68103d [diff] |
Build using non-staging Eclipse 4.5 target Since staging will become Eclipse 4.6 (Neon) we should switch to building using the stable 4.5 target. Change-Id: I8bcfde64f769510150dc3517b9931521522efdbc Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-on: https://git.eclipse.org/r/50984 Reviewed-by: Hudson CI Reviewed-on: https://git.eclipse.org/r/51065
This source tree contains the source code for the Trace Compass plugins for Eclipse.
The plugins are categorized as follows:
org.eclipse.tracecompass.analysis.* | Generic extensions to the base framework org.eclipse.tracecompass.btf.* | Best Trace Format (BTF) integration org.eclipse.tracecompass.ctf.* | Common Trace Format (CTF) reader library org.eclipse.tracecompass.gdbtrace.* | Support for reading and viewing GDB traces org.eclipse.tracecompass.lttng2.* | LTTng 2.x integration org.eclipse.tracecompass.pcap.* | libpcap integration org.eclipse.tracecompass.rcp.* | Code specific to the RCP version org.eclipse.tracecompass.statesystem.* | State System library org.eclipse.tracecompass.tmf.* | Core framework
See the plugins.svg file for a diagram showing the dependencies between the different plugins.
To set up the environment to build Trace Compass from within Eclipse, see this wiki page: http://wiki.eclipse.org/Trace_Compass/Development_Environment_Setup
To build the plugins manually using Maven, simply run the following command from the top-level directory:
mvn clean install
The default command will compile and run the unit tests. Running the tests can 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 -Pbuild-rcp to the mvn command:
mvn clean install -Pbuild-rcp -Dmaven.test.skip=true
This will build the RCP for all supported architectures. The resulting archives will be placed in org.eclipse.tracecompass.rcp.product/target/products.
These commands will also build the p2 update site, which will be placed in org.eclipse.tracecompass.releng-site/target/repository.
The following Maven profiles, and their corresponding properties, are defined in the build system. You can set them by using -P[profile name] and -D[property name]=[value] in mvn commands.
-Pctf-grammar
Re-compiles the CTF grammar files. This should be enabled if you modify the .g files in the ctf.parser plugin.
-Pbuild-rcp
Builds the RCP archives. Refer to the previous section for details.
-Pdeploy-rcp
Mainly for use on build servers. Copies the generated RCP archives, as well as the RCP-specific update site, to the paths specified by -DrcpDestination=/absolute/path/to/destination and -DrcpSiteDestination=/absolute/path/to/destination, respectively. Must be used with -Pbuild-rcp!
-Pdeploy-update-site
Mainly for use on build servers. Copies the standard update site (for the Eclipse plugin installation) to the destination specified by -DsiteDestination=/absolute/path/to/destination.
-Psign-update-site
Mainly for use on build servers. Signs all the generated update sites using the Eclipse signing server.
-Pdeploy-doc
Mainly for use on build servers. Copies the generated HTML documentation to the destination specified by -DdocDestination=/absolute/path/to/destination. Some directories may need to already exist at the destination (or Maven will throw related errors).
