Eclipse Community Forums: Sapphire » Various Target Platforms

Help

Home

Home » Archived » Sapphire » Various Target Platforms

Show: Today's Messages :: Show Polls :: Message Navigator

Various Target Platforms [message #725127]

Wed, 14 September 2011 04:01

Kamesh Sampath

Messages: 213
Registered: July 2009

Senior Member

I have very fundamental question,

What is the purpose of various target platforms ?

1. dev-target
2. target-helios
3. target-juno42

Can we use #2 and #3 if we use eclipse installations helios or juno-42 ?

~Kamesh

Report message to a moderator

Re: Various Target Platforms [message #725236 is a reply to message #725127]

Wed, 14 September 2011 10:39

Konstantin Komissarchik

Messages: 1077
Registered: July 2009

Senior Member

Here are some properties of dev-target install as distinct from target-* installs:

1. It contains source code for all the plugins.
2. It contains Sapphire plugins. This makes it possible to only load the plugins you want to work on into your workspace.
3. It will only be touched by commandline build if you invoke create-dev-target or another target that includes it (like quick-start). This makes it possible to leave your workspace open for many commandline build operations.

I do use target-* installs in a pinch, like when the command-line build is failing as the build will not get far enough to create dev-target in this situation (needs to finish building Sapphire).

- Konstantin

Report message to a moderator

Re: Various Target Platforms [message #725262 is a reply to message #725236]

Wed, 14 September 2011 11:29

Kamesh Sampath

Messages: 213
Registered: July 2009

Senior Member

On 09/14/2011 04:09 PM, Konstantin Komissarchik wrote:
> Here are some properties of dev-target install as distinct from target-*
> installs:
>
> 1. It contains source code for all the plugins.
> 2. It contains Sapphire plugins. This makes it possible to only load the
> plugins you want to work on into your workspace.
> 3. It will only be touched by commandline build if you invoke
> create-dev-target or another target that includes it (like quick-start).
> This makes it possible to leave your workspace open for many commandline
> build operations.
>
> I do use target-* installs in a pinch, like when the command-line build
> is failing as the build will not get far enough to create dev-target in
> this situation (needs to finish building Sapphire).
>
> - Konstantin

So if the dev-target is created properly during "ant clean-start" then
ideal target platfrom to use will be "dev-target" for all our Local
Sapphire build and development. Right ?

Report message to a moderator