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, copying launcher files to the right location to launch Eclipse. The end result of a source build is a runnable Eclipse.
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-2.0.zip builds Eclipse version 2.0
To run the scripts, see instructions below on building Eclipse using ant or building Eclipse using Eclipse.
Produces an Eclipse SDK using the Java compiler you have installed.
Parameter Name | Description |
osType | Target operating system (See supported types). |
windowSystemType | Target windowing system (See supported types). |
install (optional) | Directory where Eclipse will be built and installed. Default is the current directory. |
bootclasspath (optional) | The full path to the rt.jar to compile against. The rt.jar file is part of any JDK or JRE. Typically this parameter is only specified if you are cross compiling Eclipse. The default is the rt.jar on your path. |
target (optional) |
The Ant target from build.xml to execute. The default target is run and performs a complete fetch, build, javadoc build and install. Other valid targets are:
|
For example to update org.eclipse.pde source with the contents of HEAD set the tag attribute as follows:
<cvs cvsRoot=":pserver:anonymous@dev.eclipse.org:/home/eclipse" dest="${install}/plugins" package="org.eclipse.pde" tag="HEAD" quiet="${quiet}"/>
To update org.eclipse.pde source with the contents in the tag v20020618 set the tag attribute as follows:
<cvs cvsRoot=":pserver:anonymous@dev.eclipse.org:/home/eclipse" dest="${install}/plugins" package="org.eclipse.pde" tag="v20020618" quiet="${quiet}"/>
Note that since the build currently does a checkout and not an update files containing local changes will not be changed. Your local changes will be preserved but will not be merged with incoming changes. You will also not be able to commit local changes from the source build checked out files since they are all checked out as the anonymous user.
Produces an Eclipse SDK compiled with the Eclipse Java compiler and built in Ant support.
-Dos=<osType>,-Dws=<windowingSystemType>,[-Dinstall=<install>],[-Dbootclasspath=<bootclasspath>]Where:
Parameter Name Description osType Target operating system (See supported types). windowSystemType Target windowing system (See supported types). install (optional) Directory where Eclipse will be built and installed. Default is the current directory. bootclasspath (optional) The full path to the rt.jar to compile against. The rt.jar file is part of any JDK or JRE. Typically this parameter is only specified if you are cross compiling Eclipse. The default is the rt.jar on your path.
For example: Dos=win32,-Dws=win32,-Dinstall=c:\sourcebuild\foo
For example to update org.eclipse.pde source with the contents of HEAD set the tag attribute as follows:
<cvs cvsRoot=":pserver:anonymous@dev.eclipse.org:/home/eclipse" dest="${install}/plugins" package="org.eclipse.pde" tag="HEAD" quiet="${quiet}"/>
To update org.eclipse.pde source with the contents in the tag v20020618 set the tag attribute as follows:
<cvs cvsRoot=":pserver:anonymous@dev.eclipse.org:/home/eclipse" dest="${install}/plugins" package="org.eclipse.pde" tag="v20020618" quiet="${quiet}"/>
Note that since the build currently does a checkout and not an update files containing local changes will not be changed. Your local changes will be preserved but will not be merged with incoming changes. You will also not be able to commit local changes from the source build checked out files since they are all checked out as the anonymous user.
- fetchAll
- compile (compiles Java code and generates javadoc)
- buildDoc (creates doc.zip files in *.doc.isv and *.doc.user plug-ins)
- install
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.
Operating System (OS) | Windowing System (WS) |
win32 | win32 |
linux | motif |
linux | gtk |
solaris | motif |
aix |
motif |
hpux | motif |
qnx | photon |