[galileo] HowTo define a (complex) Target Platform

Part 5 of my Galileo Reviews around Target Platforms. An Overview of this blog series can be found here.

You have successfully defined a Target Platform for Riena following part 4 of this series. But that was only a very simple definition – all was based on one location: the Galileo Software Site.

Target Platform Locations

But there are more kinds of Target Platform locations.

Add Locations lets you select sources where the Plug-ins come from:

target add content location

  • from Software Site (we already did this)
  • from Installation
  • from Features
  • from Directories

Add Plug-Ins from another Eclipse Installation

Thats really cool :-) you can select one of your Eclipse Installations and select this as your Source.

As you already know I’m just working from a Cocoa-64-bit SDK Installation. There’s another Eclipse 3.5 Installation on my disk: Eclipse EPP RCP Cocoa-32-bit:

select installation rcp 32

Select your Eclipse Installation Folder.

Next >” gives you a preview of the content:

select installation rcp 32 preview content

Finish” adds the Location to your current Target definition:

target definition w location from installation

Add Plug-ins from Features of other Eclipse Installations

Instead of selecting a complete Installation you can also select one or more Features of an Installation:

target platform add features from rcp32

As before you select the Eclipse Folder of an Installation and then you’ll see the list of the Features contained at this Eclipse Installation.

Normaly the list contains only the highest available versions. Sometimes you want to define a Target Definition from older Versions: then you have to check “use specific version

You can select one or more Features and click “Finish” to add them to your current Target definition.

target definition w location from features

Add Plug-ins from 3rdParty Software Site

You can also add as much Plug-ins as you need from as much Software Sites as you need.

As described in an earlier blog of this series you define all your SoftwareSites under Preferences.

Let’s try the UpdateSite Ed Merks blogged about: “Galileo Plus

software site galileo plus

Select what you need – after clicking “Finish” your Locations look like:

target definition w location from sites

Add Plug-ins from Directories

As last option you can choose Plug-ins (bundles) stored in Directories. This is very handy if a Plug-in provider has no Software Update sites and provides only downlaods.

Choose a folder containing Plug-ins (bundles):

target add content from directory

Clicking on “Next >” gives you a preview:

target add content from directory preview

Click on “Finish” to add the content to your Target Definition.

target definition w location from directory


Fine-tuning your selected Plug-ins (bundles)

Now we have made selections from different kind of locations: Directory, Installation, Feature and Software Site.
You can do some fine-tuning we’ll talk about in my next blog “Manage Plug-ins (bundles) in Eclipse Target Platform

2 responses

  1. Very useful article, Ekke, thank you! Before 3.5, target definitions and the fact that they are completely unrelated to PDE/Build has always bothered me. This is certainly a lot better with Galileo.

    One thing you may want to add to your article is the fact that you can refer to a Target Platform location as a path relative to a project in the workspace, using
    ${project_loc:MyProject}/SomePath
    I find this really useful if you put the target under revision control, as you are now completely independent of absolute paths. Handy if you occasionally develop on a different OS, where all the directories from your revision control system map to different places. But if everything is relative to a project, who cares.

    Anyway, keep up the good work, I have learned a lot from you!

    • Jan, thanks for the kudos :-)

      and for the info how to refer to TargetPlatform Locations relative to Projects from workspace.

      I always store my TargetPlatform Locations outside the workspace and refer to it using String Substitution ($target-root),
      because I’m using same locations from different workspaces.

      ekke

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 1,121 other followers

%d bloggers like this: