Skip to main content
Jump to: navigation, search

Difference between revisions of "SMILA/Documentation/HowTo/Howto set up dev environment"

(Setup an own Eclipse instance/installation for building)
(Setup an own Eclipse instance/installation for building)
Line 21: Line 21:
 
## Menu: Help / Software Updates / Manage configuration
 
## Menu: Help / Software Updates / Manage configuration
 
## add extension location and choose the folder SMILA.extension/eclipse from smila project folder
 
## add extension location and choose the folder SMILA.extension/eclipse from smila project folder
# set the <tt>configs</tt> perperty in  the <tt>build.properties</tt> file to you setup. That is:
 
#*Windows
 
#:<tt>
 
#:: configs=win32,win32,x86
 
#:: # ...
 
#:</tt>
 
#*Linux
 
#:<tt>
 
#:: configs=linux,gtk,x86
 
#:: # ...
 
#:</tt>
 
#:Note: The default is to build for both, windows and linux platforms. However, for this to work locally the eclipse must have the corresponding plugins installed. If this is not the case  you will end up on Windows with:
 
#:<tt>...
 
#:[java] D:\Program Files\eclipse33\eclipse-SDK-3.3.2-win32-smila-build\eclipse\plugins\org.eclipse.pde.build_3.3.2.v20071019\scripts\genericTargets.xml:85: Unable to find plug-in: org.eclipse.core.filesystem.linux.x86_0.0.0. Please check the error log for more details.</tt>
 
  
 
==== Building smila ====
 
==== Building smila ====

Revision as of 12:19, 29 January 2009

Howto set up dev environment

dev env

Howto build and test locally

Setup an own Eclipse instance/installation for building

Setting up an own instance is recommended such that no extensions/features u might have installed in ur eclipse instance u use for developing interferes with the build. It probably also makes the build a little faster as the headless start of eclipse takes less time due to fewer plug-ins installed.

  1. Download an eclipse SDK, starting with at least eclipse-SDK-3.3.2-win32.zip
  2. download eclipse-RCP-3.3.2-delta-pack.zip from [1]
  3. unzip the archive and copy org.eclipse.equinox.executable_<version> from features into your features folder under your eclipse installation.
  4. start that eclipse and add sole extension location to WC /SMILA.extension by:
    1. Menu: Help / Software Updates / Manage configuration
    2. add extension location and choose the folder SMILA.extension/eclipse from smila project folder

Building smila

This folder SMILA.builder contains everything needed to build SMILA and/or run all tests locally.

Whether u build from command line or from eclipse, in both cases the make.xml ant script is executed. Before execution certain properties need to be set to meet the local setup.

For the build from eclipse u pass in these values via the command line text box in the launch config on the command line these are set in a shell script.

Building SMILA from within eclipse
  1. select the SMILA.builder bundle
  2. open External Tools Dialog
  3. create a new ant build configuration or choose your configuration if exists
  4. choose the build file of this bundle, e. g. ${workspace_loc:/SMILA.builder/make.xml}
  5. insert the following arguments (but adapt these to your setup)
    -DbuildDirectory=D:/eccenca/SMILA/eclipse.build
    -Declipse.home=D:/eclipse33
    -Dbuilder=D:/eccenca/SMILA/SMILA.builder
    -Declipse.running=true
    -DpdeBuildPluginVersion=3.3.2.v20071019(default)
    -DequinoxLauncherPluginVersion=1.0.1.R33x_v200080118(default)
    -Dos=win32 -Dws=win32 -Darch=x86
    -Dtest.java.home=D:/java/jre1.5.0_11
  6. Apply, close and run SMILA.builder with this external tool configuration
Building SMILA from command line

The make.bat (or .sh) is just a shell script to set the properties that are need for the ant script.

Steps:

  1. adjust all paths in \SMILA.builder\make.bat according to own setup
  2. execute make.bat

The whole process takes about 15 minutes at the time of writing, so be patient or get some java-like beverage ;)

run junit tests for osgi bundles

  • Plugin Junit Launch config
  • write config.ini and ref it from lauch config.
    tip: use \ to brake up long lines to have better overview
  • share the launch config

For further information see: Development Guidelines

Back to the top