<p>Install Ant, 1.6 JDK, and a CVS client, as per each program's instructions. Minimally

+

<p>Install Ant 1.7, JDKs, and a CVS client, as per each program's instructions. Minimally

you will need the following environment variables set.</p>

you will need the following environment variables set.</p>

<ol>

<ol>

Line 32:

Line 33:

<li>Set the JAVA_HOME environment variable to the root of your <B>1.6 JDK</B> installation.</li>

<li>Set the JAVA_HOME environment variable to the root of your <B>1.6 JDK</B> installation.</li>

<li>Set the ANT_HOME environment variable to the root of your Ant installation.</li>

<li>Set the ANT_HOME environment variable to the root of your Ant installation.</li>

−

<li>If you are fetching the source from CVS, set the CVS_RSH=ssh

+

<li>If you are fetching the source from CVS, export the CVS_RSH=ssh

−

+

</ol>

</ol>

−

<h4>Run the Build</h4><ol>

+

+

<h4>Run the Build</h4>

+

<ol>

<li>Extract the eclipse-sourceBuild-*.zip to a directory. Extract using tar if using a *nix drop.</li>

<li>Extract the eclipse-sourceBuild-*.zip to a directory. Extract using tar if using a *nix drop.</li>

−

<li>Put the eclipse-SDK-your-platform.[zip|tar.gz] in the same directory where you extracted the source build.

+

<li>Put the eclipse-SDK-your-platform.[zip|tar.gz] in the same directory where you extracted the source build.</li>

−

<li>Update the build.properties file included at the root of this zip to point to the bootstrap classpath of your 1.4, 1.5, and 1.6 JDK locations.

+

<li>Update the org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/sdk/srcBuild/build.properties file included to point to the bootstrap classpath of your 1.4, 1.5, and 1.6 JDK locations. You'll also have to update it to include the location of your CDC 1.0 and CDC 1.1 foundation class libraries. If you don't have access to the CDC libraries, you can update the properties file to point to the 1.5 vm for the CDC variables.</li>

−

You'll also have to update it to include the location of your CDC 1.0 and CDC 1.1 foundation class libraries. If you don't have access to these libraries, you can update the properties file to point to the 1.5 vm for the CDC locations.

note: MapVersionTag is only required if you want to checkout a specific version that relates to a build. For instance, if you wanted to recreate the integration build from I20090811-0800, you could set the mapVersionTag=I20090811-0800 when running a the source fetch build.

+

+

+

<li>If running the sourceFetch build, cd to the buildScripts directory.</li>

<td width="30%">bootclasspath (optional)</td><td width="70%">The default list of bootclasspath jars to compile against using

+

<tr>

−

either a colon or semi-colon as separators. The jars that make up a

+

<td>bootclasspath (optional)</td><td>The default list of bootclasspath jars to compile against using either a colon or semi-colon as separators. The jars that make up a bootclasspath are part of any JDK or JRE. Typically this parameter is only specified if you are cross compiling Eclipse. The default is set to the jars in the JDK or JRE in JAVA_HOME.</td>

−

bootclasspath are part of any JDK or JRE. Typically this parameter is

+

</tr>

−

only specified if you are cross compiling Eclipse. The default is set to the

+

</table>

−

jars in the JDK or JRE in JAVA_HOME.</td></tr>

+

−

<td width="30%">target (optional)</td><td width="70%">

+

<h4>Install Eclipse</h4>

−

<p>The Ant target from build.xml to execute. The default target is <b>run</b>

+

<p>When the Eclipse build is complete, there will be a zip file called</p>

−

and performs a complete fetch, build, javadoc build and install. Other

+

<p>&lt;osType&gt;-&lt;windowSystemType&gt;-&lt;architecture&gt;-sdk.zip</p><p>in the results subdirectory of your build directory. If you are building for Linux or Mac, there will be a tar.gz file. </p>

−

valid targets are:</p><ul>

+

−

<li>fetch</li><li>compile</li><li>install</li></ul></td></tr>

+

−

</table></ol><blockquote>

+

−

<p>&nbsp;</p></blockquote></ol><p><b>Install Eclipse</b></p><p>When the Eclipse build is complete, there will be a zip file called</p><p>&lt;osType&gt;-&lt;windowSystemType&gt;-&lt;architecture&gt;-sdk.zip</p><p>in the results subdirectory of your build directory. If you are building for Linux or Mac, there will be a tar.gz file. </p></p>

+

<p>Extract this file to the directory where you would like to run Eclipse. If

<p>Extract this file to the directory where you would like to run Eclipse. If

Line 83:

Line 100:

<td width="48%">Operating System (os)</td>

<td width="48%">Operating System (os)</td>

<td width="52%">Windowing System (ws)</td>

<td width="52%">Windowing System (ws)</td>

−

<td width="52%">Archecture</td>

+

<td width="52%">Architecture</td>

</tr>

</tr>

<tr>

<tr>

Line 152:

Line 169:

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

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 soft links).</li>

and make the appropriate soft links).</li>

−

<li>Only Java source code is compiled. *.dll, *so, *sl and Eclipse executables are all checked out of dev.eclipse.org prebuilt in this build process. The instructions on recompiling the [http://www.eclipse.org/swt/faq.php#buildeclipseexe eclipse executable] and [http://www.eclipse.org/swt/faq.php#buildeclipseexe recompling swt libraries] available in the

+

<li>Only Java source code is compiled. *.dll, *so, *sl and Eclipse executables are all checked out of dev.eclipse.org and prebuilt in this build process. The instructions on recompiling the [http://www.eclipse.org/swt/faq.php#buildeclipseexe eclipse executable] and [http://www.eclipse.org/swt/faq.php#buildeclipseexe recompling swt libraries] available in the

[http://www.eclipse.org/swt/faq.php SWT FAQ] are also a useful reference. This document also includes a list of the prerequisites for running SWT on

[http://www.eclipse.org/swt/faq.php SWT FAQ] are also a useful reference. This document also includes a list of the prerequisites for running SWT on

Running Eclipse Source builds for 3.5 (Source from CVS)

What is an Eclipse Source Build?

Eclipse source builds provide developers with an automated method for checking out source code and other required resources, compiling the Java code, generating
javadoc, and finally, creating a zip file of an Eclipse runtime from a downloaded source tree. The end result of a source build is a runnable Eclipse.

Getting the Source

A source build download contains shell and ant scripts that fetch and build a particular version of Eclipse. Although you can manually edit build.xml files
in each feature and plug-in, they are typically generated by the Eclipse pde-build plug-in. As a result you will need to download a fresh source build zip file
when major changes occur to Eclipse source, such as the addition or removal of plug-ins. The version of Eclipse a particular source build will create is
embedded in the source build zip file name. For example, eclipse-sourceBuild-I20090624.zip builds Eclipse from integration build 20090624.

An Eclipse SDK build zip that matches that platform and buildId of the platform you're attempting to build. For instance, if you're building I20090611-1540 for linux.gtk.x86, you should download eclipse-SDK-I20090611-1540-linux-gtk.tar.gz to compile the build. You will use these bundles to compile a new SDK from source. Confusing, huh?

Initial Setup

Install Ant 1.7, JDKs, and a CVS client, as per each program's instructions. Minimally
you will need the following environment variables set.

Add the Ant bin directory, and the CVS executable to your path.

Set the JAVA_HOME environment variable to the root of your 1.6 JDK installation.

Set the ANT_HOME environment variable to the root of your Ant installation.

If you are fetching the source from CVS, export the CVS_RSH=ssh

Run the Build

Extract the eclipse-sourceBuild-*.zip to a directory. Extract using tar if using a *nix drop.

Put the eclipse-SDK-your-platform.[zip|tar.gz] in the same directory where you extracted the source build.

Update the org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/sdk/srcBuild/build.properties file included to point to the bootstrap classpath of your 1.4, 1.5, and 1.6 JDK locations. You'll also have to update it to include the location of your CDC 1.0 and CDC 1.1 foundation class libraries. If you don't have access to the CDC libraries, you can update the properties file to point to the 1.5 vm for the CDC variables.

note: MapVersionTag is only required if you want to checkout a specific version that relates to a build. For instance, if you wanted to recreate the integration build from I20090811-0800, you could set the mapVersionTag=I20090811-0800 when running a the source fetch build.

The default list of bootclasspath jars to compile against using either a colon or semi-colon as separators. The jars that make up a bootclasspath are part of any JDK or JRE. Typically this parameter is only specified if you are cross compiling Eclipse. The default is set to the jars in the JDK or JRE in JAVA_HOME.

Install Eclipse

When the Eclipse build is complete, there will be a zip file called

<osType>-<windowSystemType>-<architecture>-sdk.zip

in the results subdirectory of your build directory. If you are building for Linux or Mac, there will be a tar.gz file.

Extract this file to the directory where you would like to run Eclipse. If
you extract it to your root directory, a directory called eclipse will be created. <p>
<p>Run Eclipse with the desired command line parameters.

Supported Platforms

Eclipse can be built on any of the following platforms. With some limitations
any platform can be used to build Eclipse for any or all supported platforms. To see the latest information on the platforms supported for a given release, refer to the latest Eclipse Project Plan.

Operating System (os)

Windowing System (ws)

Architecture

win32

win32

x86

win32

wpf

x86

linux

gtk

x86

linux

gtk

x86_64

linux

gtk

ppc

macosx

carbon

ppc

macosx

cocoa

x86

macosx

cocoa

x86_64

aix

motif

ppc

solaris

gtk

sparc

linux

gtk

s390

linux

gtk

s390x

Known Limitations

Building unix flavours of Eclipse on Windows will result in incorrect file permissions. The *.so, *.sl, and Eclipse executable files will not have
execute permissions. In addition, linux-motif and linux-gtk builds will not have soft links to libXm.so.2.1 in the installation root directory. 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 soft links).

Only Java source code is compiled. *.dll, *so, *sl and Eclipse executables are all checked out of dev.eclipse.org and prebuilt in this build process. The instructions on recompiling the eclipse executable and recompling swt libraries available in the
SWT FAQ are also a useful reference. This document also includes a list of the prerequisites for running SWT on
Linux GTK

For the platforms where JDK 1.6 support is not yet available e.g linux-gtk-s390, linux-gtk-s390x the Eclipse SDK can be built with JDK
1.5 in place JDK 1.6. To do that, please follow the following steps:

and package the plugins that require JDK 1.6 currently:
org.eclipse.jdt.compiler.tool, org.eclipse.jdt.compiler.apt and
org.eclipse.jdt.apt.pluggable.core from the files
features/org.eclipse.jdt/feature.xml and