Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Linux Tools Project/Eclipse Build"

(Eclipse Build: Why And How)
(Prerequisites for building with eclipse-build)
Line 14: Line 14:
 
== Prerequisites for building with eclipse-build ==
 
== Prerequisites for building with eclipse-build ==
 
* A 1.6 JDK installed in a standard place (see build.properties)
 
* A 1.6 JDK installed in a standard place (see build.properties)
 +
: to check that execute a command
 +
java -version
 
* Ensure JAVA_HOME is set (e.g., export JAVA_HOME=/usr/lib/jvm/java)
 
* Ensure JAVA_HOME is set (e.g., export JAVA_HOME=/usr/lib/jvm/java)
 +
: to check that execute a command
 +
echo $JAVA_HOME
 +
: to set the variable call
 +
JAVA_HOME=<path to your java>
 +
: usually
 +
JAVA_HOME=/usr/lib/jvm/java/
 
* Ant version 1.8.2 or newer
 
* Ant version 1.8.2 or newer
 
* bash, sh, perl, sed, rsync, below requirements for particular distro
 
* bash, sh, perl, sed, rsync, below requirements for particular distro

Revision as of 04:34, 3 January 2012

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

Linux Tools
Website
Download
Community
Mailing ListForumsIRCmattermost
Issues
OpenHelp WantedBug Day
Contribute
Browse Source

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

Eclipse Build: Why And How

When building, Eclipse normally satisfies its third party requirements by using libraries provided in Orbit. Orbit provides pre-built libraries which have been made into OSGi bundles with proper versioning, etc.

The problem for some Linux distributions is that they cannot use the pre-built binaries provided by Orbit. Eclipse must be built using the binaries provided in that distribution.

For more information about how Eclipse Build works please refer to the Eclipse Build Inner Workings Page

Prerequisites for building with eclipse-build

  • A 1.6 JDK installed in a standard place (see build.properties)
to check that execute a command
java -version
  • Ensure JAVA_HOME is set (e.g., export JAVA_HOME=/usr/lib/jvm/java)
to check that execute a command
echo $JAVA_HOME
to set the variable call
JAVA_HOME=<path to your java>
usually
JAVA_HOME=/usr/lib/jvm/java/
  • Ant version 1.8.2 or newer
  • bash, sh, perl, sed, rsync, 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 tarballs of the SDK sources (and optionally the SDK test sources and SDK test scripts) from the eclipse-build downloads area 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 git clone of eclipse-build

Submitting patches

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).

Build Debs from upstream source

These instructions are a kludge and not best practice, but they should get you a deb, hopefully.

  1. Get the eclipse build from the Git repository as detailed in the "get from source section" above
  2. Comment out the delete configuration section in the build.xml?
  3. Get the eclipse SDK/PDE source from the download site listed above, and put in the eclipse-build directory, and a copy underneath the
  4. Get the debian directory from master-3.6 out of the java-pkg on git.debian.org
    1. put the debian directory inside the build eclipse directory
    2. in the debian directory edit changes as appropriate
  5. run dpkg-buildpackage -rfakeroot -us -uc -b
  6. Cross fingers and hope it works
  7. Go away and a have a coffee, and do the laundry; it will take about 30 minutes to compile on Core Duo
  8. Hopefully you'll have your shiny deb files for eclipse

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

Planned items

  • Move away from dropins for JDT, PDE, etc.
  • 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.

Back to the top