CDT/Obsolete/release engineering

What do we build today?

CDT is currently built as an update site, archived in a master zip file.

To install CDT:

1. Download the master zip file and put it somewhere on your machine.
2. Fire up Eclipse (The Platform Run-time 3.4 is minimum recommended)
3. Help->Software Updates
4. On the Available Features tab, select Manage sites...
5. Add... in the master zip as an Archive...
6. Under CDT Main Features select the one you want. C/C++ Development Tools is the main one. The SDK adds in the schemas and source for building extensions to the CDT. The C/C++ Development Platform is the Tools without the GNU toolchain support.
7. You can install other neat things, including the Mylyn bridge, from the CDT Optional Features category.

This master zip has everything, including:

• CDT Platform Feature - includes editor, search, builders, launch, debug, user documentation
• CDT Runtime Feature - superset of platform feature that adds gnu toolchain integrations for build/debug
• CDT SDK Feature - superset of runtime that adds source and extension point schemas
• GDB Hardware Debugging - provides a launch configuration for launching gdb to do hardware debugging.
• XL C/C++ Compiler Support - provides an error parser and managed build support for IBM's XL C/C++ compilers.
• LR Parser - provides a parser for the ISO/IEC 9899:1999 variant of the C programming language (aka C99) and the C++ programming language, generated from a grammar using the LPG parser generator. The grammar can be reused and extended to create your own parser for variants on the C programming language.
• Unified Parallel C Support - Provides support for the Unified Parallel C programming language. Provides parsing/indexing infrastructure and language definition, allowing the UPC language to be recognized by CDT. Requires the LR parser feature.
• Mylyn Bridge - allows CDT to work with Mylyn.
• CDT Utilities - provides utilities for C/C++ Development Tools
• CDT Testing Feature - includes all test plugins required for running automated JUnit tests

How often do we build?

The current build schedule is every Friday morning at 6am EDT for the HEAD stream (CDT 6.0) and the same day at 8am EDT for the cdt_5_0 stream (CDT 5.0.2).

Builds against older streams are available upon request.

How do we run the build?

We use several scripts to kick off our builds. There is one for every CVS stream we build against in /home/www/tools/cdt/scripts/ on the Eclipse build machine (build.eclipse.org, running Linux/PPC):

Script	CDT version	CVS stream	Java JRE
cdtbuild	CDT 6.0	HEAD	Java 5
cdtbuild5.0	CDT 5.0.2	cdt_5_0	Java 5

These scripts setup the staging area on the build machine for the build. Each of these scripts checks out the latest org.eclipse.cdt.releng plugin in their respective stream. It then runs build.sh and build.xml (in org.eclipse.cdt.releng) where majority of the build logic resides.

We rely on the plugins in org.eclipse.releng.basebuilder to run our builds. We use different versions of the basebuilder for various stream builds. More information can be found on the following page:

http://wiki.eclipse.org/Platform-releng-basebuilder

During the build process, features and plugins are tagged in CVS with the build timestamp. Once the build is completed, it is signed, (JUnit) tested, and made available in the CDT download area .

How do we publish release builds?

1. Unzip the master zip into a temporary directory
2. Move the plugin and feature jars into the update site (cdt/releases/[release_name])
3. Insert the features into the update site’s site.xml and set categories as appropriate
4. Run the optimize script that’s in the cdt/scripts directory to create packed jars
5. Wait for the downloads site to update and test that the site.xml is correct (this could take a while)
6. Update the cdt website, send mail to cdt-dev and cdt newsgroup announcing new build
7. Tag the build in CVS