Setup

1. Add the zip, unzip, tar, gzip and cvs executables to your path as required.
2. Add the jre/bin directory
of the installed JDK to your path.
3. Check out org.eclipse.releng.basebuilder and org.eclipse.releng.eclipsebuilder into a directory.

Run the Build

cd to org.eclipse.releng.eclipsebuilder directory and execute
the following command (currently the build.xml script can only be executed in
a headless eclipse due to bug 35923

scripts used to build any or all configurations of the Eclipse Platform without

source and developer documentation.

sdk.rcp

This directory contains the scripts used to build the RCP SDK. The RCP SDK is comprised

of the base RCP plug-ins and the org.eclipse.platform.source plug-in. This build
can only be executed in a buildDirectory where the Eclipse SDK was previously

built.

rcp

This directory contains
the scripts used to build any or all configuration of the Eclipse RCP plug-ins.

jdt.sdk

This directory contains the scripts

used to build the platform-independant and/or the Mac OSX configuration of the
Eclipse Java Development Tooling SDK. The Eclipse JDT SDK component contains binaries,

source, user and developer documentation.

jdt

This directory contains the scripts used to build the platform-independant and/or the Mac OSX configuration of the Eclipse Java Development Tooling component without
source and developer documentation.

pde.sdk

This

directory contains the scripts used to build the Eclipse Plug-in Development Environment

to build the Eclipse Plug-in Development Environment component without source

and developer documentation.

sdk.examples

This

directory contains the scripts used to build the platform-independant and/or the
Windows configuration of the Eclipse Examples. The Eclipse Examples contain binaries

and source.

sdk.tests

This

directory contains the scripts used to build the Eclipse Automated testing environment
which contains the test framework plug-ins, JUnit test plug-ins and scripts used

to launch the JUnit tests from the command line.

test.framework

This

directory contains the scripts used to build the Eclipse test framework plug-ins

only.

Ant Properties

<p>
Settings in a component's build.properties. The following properties
are pre-defined in the build.properties file for the specified component. They
can be overridden by setting them at the command line at build time or by changing

them directly in the component's build.properties file.

Name

Description

baseos,basews,basearch

The

os, ws and arch values of a pre-built eclipse component being compiled against.

See list of possible values in the table of <a href="#buildconfigs">build configurations</a>.

baseLocation

A directory separate from

buildDirectory which contains pre-built plugins and features against which to
compile. The basedirectory must not contain any features, plugins or fragments

which are already or will be located in the buildDirectory (see below).

<javac> task</a> in a plugins' build.xml. Default set to ${java.home}/lib/rt.jar.

buildDirectory

The absolute path to a

working directory where the source for the build will be exported, where scripts
will be generated and where the end products of the build will be located. On
Windows systems, the path length should not exceed thirty characters due to path

length limitations when compiling some classes in eclipse.

buildId

The
build name. Default set to "build".

buildLabel

Refers

to the name of the directory which will contain the end result of the build. Default
set to ${buildType}.${buildId}, ie."I.build". This directory will be

created inside the location specified by the ${buildDirectory} property.

buildType

Letters I, N, S, R or M are used in Eclipse builds

to identify builds as being one of the following:

I - Integration

N - Nightly S - Stable R - Release M - Maintenance

If

set to N, all source will be checked out from the HEAD stream. In all other cases,
tags as specifed in map files will be used when exporting plugins to the buildDirectory.

archivePrefix

The name of the top level directory
which should exist in the produced zip file. Typically set to "eclipse".

collectingFolder

The name of the top level directory where the
built features and plugins will be gathered. This is typically set to "eclipse".

the map files used for a previous integration build. Typically, these tags are
in the form "v<date/timestamp>" for example "v200307110800"
will checkout the map files used to run the integration at the specified date/time.

These scripts work with 3.0 stream builds > 20030701.

timestamp

A timestamp used to fill in value for buildid in about.mappings

files. The timestamp is also used to tag the org.eclipse.releng project on dev.eclipse.org
only when an appropriate value for mapCvsRoot is provided and when the tagMaps

So by default, these nine configurations of the Eclipse Platform will be
built if the "configs" property is not overwritten at the command line.

Although it is possible to build for all configurations on one machine,
building Unix flavours of Eclipse on Windows will result in missing execute permissions
and missing symbolic links. In these cases you would have to write an install
or post install script to set permissions properly. (UNIX builds built on UNIX
systems will set sufficient permissions and make the appropriate links). <p>

Examples

<p>

Build Windows SDK component on Windows

<p><b>java -cp ..\org.eclipse.releng.basebuilder\startup.jar
org.eclipse.core.launcher.Main -application org.eclipse.ant.core.antRunner -buildfile
build.xml -Dcomponent=sdk -Dconfigs="win32,win32,x86" -Djavacfailonerror=true
-DjavacVerbose=false -DbuildDirectory=c:\mybuild
This builds an eclipse
SDK for the windows configuration only in the directory c:\mybuild. "-DjavaVerbose=false"
indicates that no compile logs will be generated and "-Djavacfailonerror=true"
will cause the build to fail if there are any compile errors.

This builds an eclipse SDK for the linux gtk and linux motif configurations.
By default the buildDirectory will be set "src" in eclipse.releng.eclipsebuilder.
"-Dzipargs=-y" is used here to preserve the symbolic links libXm.so
and libXm.so.2 in the Linux Motif root directory of eclipse. The symbolic links
will only be created at build time if the build is run on a Linux operating system.

This is a command that can be used to build an eclipse SDK for the windows
configuration on a *nix system. A bootclasspath pointing to a Windows rt.jar is
explicitly specified so that bootstrap classes not available in the *nux virtual
machine are available to compile windows specific classes in Eclipse. By default
the buildDirectory will be set "src" in eclipse.releng.eclipsebuilder.

<p>java -cp ..\org.eclipse.releng.basebuilder\startup.jar org.eclipse.core.launcher.Main
-application org.eclipse.ant.core.antRunner -buildfile build.xml -Dcomponent=jdt
-Dconfigs="*,*,*" -DbuildDirectory=c:\builds\jdt -DbaseLocation=c:\builds\platform
-Dbaseos=win32 -Dbasews=win32 -Dbasearch=x86 -Djavacfailonerror=true
<p>This builds an Eclipse JDT component against a pre-built eclipse platform plugins.
The build will fail if there are compile errors. The value specified for baseLocation
must not contain any JDT features or plugins or the build will fail. "baseos",
"basews" and "basearch" should be specified in order to find
the correct location of platform specific jars (i.e. swt.jar) on the classpath.

builds an Eclipse JDT component in the same directory where a Windows platform
configuration was previously built. The build will fail if there are compile errors.
"baseos", "basews" and "basearch" should be specified
in order to find the correct location of platform specific jars (i.e. swt.jar)
on the classpath.