Revision as of 10:08, 25 March 2011

{{#eclipseproject:technology.linux-distros}}

Eclipse-build aims to ease the building of the Eclipse SDK for Linux distributions.

Prerequisites for building with eclipse-build

• A 1.6 JDK installed in a standard place (see build.properties)
• Ensure JAVA_HOME is set (e.g., export JAVA_HOME=/usr/lib/jvm/java)
• Ant version 1.7.1 or newer
• bash, sh, perl, sed, below requirements for particular distro
• icu4j; jsch; java.servlet 2.5; javax.servlet.jsp 2.0; Apache Commons: codec, EL, httpclient, logging; jasper; lucene; hamcrest; jetty; ASM; SAT4J
• At least 3 GB of storage available
• Xvnc (Fedora: tigervnc-server package) if you want the tests to run and not touch your main display

How To build Eclipse SDK with eclipse-build released tarballs

• Download and extract the latest eclipse-build*.tar.gz (pick the appropriate directory for the release you want)
• Download the SDK and SDK tests source tarballs from the same directory and put them in the eclipse-build* directory. NOTE: eclipse-build provides source tarballs created from the same tag as the official releases but with additional sources needed for the build.
• Run ant (you will likely need to ensure that JAVA_HOME points to your JDK installation directory)

If the build finishes without error there will be a build/eclipse-$YOUR_BUILD_ID-src/installation directory containing a ready-to-use Eclipse SDK. Eclipse-build is verified to work on x86, x86_64 and ppc architectures. Eclipse-build has been successfully tested on Fedora, Debian, Ubuntu, Gentoo, and RHEL. Refer to distribution-specific instructions below. We are interested in reports of success on other distributions. Please let us know via linuxtools-dev@eclipse.org.

Optional: ant runTests. Look for test results (a few hours running time) in tests_<timestamp>/results/html/org.eclipse.sdk.tests.html.

How to build Eclipse SDK from checked out eclipse-build trunk

• The following SVN commands can easily be replaced with checking things out in Eclipse (say, with this handy PSF (help on PSFs)). The command-line actions afterwards can be executed from a terminal. It is preferred that patches are generated from within Eclipse. All patches must be submitted via http://bugs.eclipse.org eclipse.org bugzila
• svn co http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/eclipse-build/trunk/eclipse-build
• svn co http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/eclipse-build/trunk/eclipse-build-config
• svn co http://dev.eclipse.org/svnroot/technology/org.eclipse.linuxtools/eclipse-build/trunk/eclipse-build-feature
• git address --> git clone http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.eclipse-build.git/
• cd eclipse-build
• ln -s ../eclipse-build-config
• ln -s ../eclipse-build-feature
• Download SDK sources as above and put them in the eclipse-build directory
• Optional: download the test sources and test scripts as above and put them in the eclipse-build directory.
• Run ant
• Check for successful build in build/eclipse-$YOUR_BUILD_ID-src/installation
• Optional: ant runTests. Look for test results (a few hours running time) in testResults-${timestamp}/html/org.eclipse.sdk.tests.html.

Submitting patches

• Check out from SVN (PSF (help on PSFs), location)
• It is preferred that patches are generated from within Eclipse. All patches must be submitted via http://bugs.eclipse.org eclipse.org bugzila

Debian/Ubuntu Build Requirements

On Ubuntu 9.10 "Karmic Koala" (and later) you can simply run "sudo apt-get build-dep eclipse && sudo aptitude install build-essential" to install those packages.

The list of build dependencies (excluding build-essential) can be found here (see Build-Depends).

Fedora Build Requirements

On Fedora, just run yum-builddep eclipse to get the build dependencies (including the dependencies to which the Fedora package is symlinked). You must also ensure you have the following installed (the latter to run the tests): patch tigervnc-server.

To-do list

• See eclipse-build open bugs
• Add an item
• In Eclipse bugzilla, watch linux.packagingtools-inbox@eclipse.org if you want to be notified of new bugs

Planned items

• Provision every feature separately so we can move them in dropins
• Add ability to build only given feature e.g org.eclipse.swt (Maybe)

Testing

See tests for how to build and run the SDK tests and to report results and check if others are working on common failures.