Building Overture Headless

From Wiki.overturetool.org

Jump to: navigation, search
Warning: These instructions are no longer entirely correct. The maven build process is presently being fixed.


This page documents the procedure used for building the binary packages of the Overture Platform that are distributed at SourceForge.

Contents

Fetching Sources

Run the following command. 

 svn checkout https://overture.svn.sourceforge.net/svnroot/overture/trunk sources

where sources is the name of the folder that contains the source.

Installing Core Maven projects

The installation is done by a script located in the sources directory.

  • Linux: 
 sh setup

gives: 

 Overture development setup
   Install: Prepare all sources for development  
   Clean  : Clean all autogenerated source
  • Windows 
 setup.bat

Installing Eclipse for Headless Build

To install Eclipse for headless build, you need to download two bundles from the [Eclipse base: http://download.eclipse.org/eclipse/downloads/ Eclipse download site]:

  • eclipse-SDK-${VERSION}-${PLATFORM}.zip
  • eclipse-${VERSION}-delta-pack.zip

where version is the Eclipse version like 3.5.2 and platform like win32. Example for 3.5.2:

When downloaded extract the eclipse-sdk and then the eclipse-delta-pack in the same folder.


Building and packing the platform

To build the platform a build script must be configured. A template can be found in the build project in the SVN.

The script needs to configure build parameters:

Build properties
Property Description Example value
platformReleaseVersion The platform version shown in the About in the platform 0.3.0
ECLIPSE_HOME The Eclipse installation to use for building c:\eclipse
BUILD_XML_PATH Path to the checked out source build file c:\sources\ide\build
equinoxLauncherPluginVersion The launcher in the ECLIPSE_HOME. 1.0.201.R35x_v20090715
pdeBuildPluginVersion The version of the pde builder plugin 3.5.2.R35x_20100114
BASEOS The OS of the host platform win32
BASEWS Windowing system of the host platform win32
BASEARCH Architecture of the host platform x86

The customized script for linux looks like: 

BUILD_DIR=${PWD}
BUILD_DIR=$BUILD_DIR/build
 
echo Building overture
 
ECLIPSE_HOME=/home/kela/Desktop/eclipse352
BASE=$ECLIPSE_HOME
BUILD_XML_PATH=/home/kela/overture/ide/build/
equinoxLauncherPluginVersion='1.0.201.R35x_v20090715'
pdeBuildPluginVersion='3.5.2.R35x_20100114'
BASEOS=linux32
BASEWS=gtk
BASEARCH=x86
 
echo Changing to build.xml directory
 
cd $BUILD_XML_PATH
 
LAUNCHER_PLUGIN=$ECLIPSE_HOME/plugins/org.eclipse.equinox.launcher_$equinoxLauncherPluginVersion.jar
 
echo Starting Eclipse ANT runner
 
java -cp $LAUNCHER_PLUGIN org.eclipse.equinox.launcher.Main -application org.eclipse.ant.core.antRunner -buildfile build.xml -Dbase=$BASE -DeclipseLocation=$ECLIPSE_HOME -DequinoxLauncherPluginVersion=$equinoxLauncherPluginVersion -DbuildDirectory=$BUILD_DIR -DpdeBuildPluginVersion=$pdeBuildPluginVersion -Dbaseos=$BASEOS -Dbasews=$BASEWS -Dbasearch=$BASEARCH
 
cd $BUILD_DIR
cd ..
echo Done
The script will buidl the platform in the directory it is started from so if the script from above is called build.sh and placed in buildDir and the following command is executed in the directory the build will start:
 sh build.sh

The buildDir will now contain the following folders

  • buildRepo: The repository for self-update
  • I.OvertureIde: The directory for all the binary which can be uploaded to SourceForge

Alternative build method for the RCP

Update the maven settings.xml located in ~/.m2 with the following properties in an active profile: 

<profile>
  <id>rcpbuild</id>
  <activation>
    <activeByDefault>true</activeByDefault>
  </activation>
  <properties>
    <user.rcp.build.base>C:\Users\kela\Downloads\eclipse362</user.rcp.build.base>
    <user.rcp.build.equinox.launcher.plugin.version>1.1.1.R36x_v20101122_1400</user.rcp.build.equinox.launcher.plugin.version>
    <user.rcp.build.pde.build.plugin.version>3.6.2.R36x_20110203</user.rcp.build.pde.build.plugin.version>
    <user.rcp.build.baseos>win32</user.rcp.build.baseos>
    <user.rcp.build.baseos>win32</user.rcp.build.baseos>
    <user.rcp.build.basearch>x86</user.rcp.build.basearch>
  </properties>
</profile>

The properties is similar to the above explanation. When this is configures the RCP can be build after the initial setup is completed including mvn eclipse:eclipse by executing: 

trunk/ide/build/mvn deploy

The RCP will then be available under target/RCP

Uploading a new version to SourceForge

(This step can only be done by users with sufficient release rights)

Upload the buildRepo to SourceForge by FTP 

Server=web.sourceforge.net
Port=21
User=USER,overture
Password=PASSWORD
Remote dir=/home/groups/o/ov/overture/htdocs/ide/repository

where:

  • USER is your SourceForge username
  • PASSWORD is your SourceForge password

Upload the binaries by rsync The binaries in the I.OvertureIde folder must be uploaded by rsync like: 

 rsync -e ssh %FILE% lausdahl,overture@frs.sourceforge.net:%DEST%

where:

  • %FILE% is the zip file
  • %DEST% is the path at sf: /home/pfs/project/o/ov/overture/Overture_IDE/0.3.x/
Retrieved from "http://wiki.overturetool.org/index.php/Building_Overture_Headless"
Personal tools