Home » Archived » Buckminster » Materializing target platform from Eclipse target definition?
|
| Re: Materializing target platform from Eclipse target definition? [message #485622 is a reply to message #485620] |
Mon, 14 September 2009 08:17   |
|
Hi Roland,
The Buckminster command 'importtargetdefinition' will import an eclipse target definition. The "materialization" as
such, is performed the same way as when you set a target definition from your IDE preferences.
A true Buckminster materialization can also be used to build a target platform. That has the advantage that you don't
need to specify the features and bundles that should be included. Buckminster figures that out by resolving the query.
You cannot use an eclipse target definition as input to this process. Instead, you would set the target platform to
point to an empty directory and use an MSPEC to control which components that should end up there during
materialization. The repositories that you'd use for input must be defined in an RMAP.
Regards,
Thomas Hallgren
On 09/14/2009 10:00 AM, Roland Tepp wrote:
> Hey,
>
> Is this possible? how woulod I go about doing this?
>
|
|
| |
| Re: Materializing target platform from Eclipse target definition? [message #485648 is a reply to message #485640] |
Mon, 14 September 2009 10:04 |
|
On 09/14/2009 11:33 AM, Roland Tepp wrote:
> Thanks for quick reply.
>
> So to get more concrete, let's say I have specified my target platform
> in my-platform.target definition and I want to materialize a set of
> products in my workspace against the specified target platform.
>
> That is - I want to set the target platform of my workspace to the one
> defined in my-platform.target and materialize the workspace based on
> some mspec/cquery.
>
> What are the steps I would have to perform to achieve that in headless
> mode (e.g. perform one-click set-up of the workspace)?
>
You would execute two commands.
buckminster importtargetdefinition my-platform.target
buckminster import my.mspec OR my.cquery
This setup will might require some redundant information though, since what you require for your TP can be derived from
the features that you materialize.
Regards,
Thomas Hallgren
> 14.09.2009 11:17, Thomas Hallgren kirjutas:
>> Hi Roland,
>> The Buckminster command 'importtargetdefinition' will import an eclipse
>> target definition. The "materialization" as such, is performed the same
>> way as when you set a target definition from your IDE preferences.
>>
>> A true Buckminster materialization can also be used to build a target
>> platform. That has the advantage that you don't need to specify the
>> features and bundles that should be included. Buckminster figures that
>> out by resolving the query. You cannot use an eclipse target definition
>> as input to this process. Instead, you would set the target platform to
>> point to an empty directory and use an MSPEC to control which components
>> that should end up there during materialization. The repositories that
>> you'd use for input must be defined in an RMAP.
>>
>> Regards,
>> Thomas Hallgren
>>
>>
>>
>> On 09/14/2009 10:00 AM, Roland Tepp wrote:
>>> Hey,
>>>
>>> Is this possible? how woulod I go about doing this?
>>>
>>
>
>
|
|
|
| Re: Materializing target platform from Eclipse target definition? [message #485653 is a reply to message #485648] |
Mon, 14 September 2009 10:54 |
|
Sorry, forgot one thing. You need to pass the option --active to the importtargetdefiniton command.
- thomas
On 09/14/2009 12:04 PM, Thomas Hallgren wrote:
> On 09/14/2009 11:33 AM, Roland Tepp wrote:
>> Thanks for quick reply.
>>
>> So to get more concrete, let's say I have specified my target platform
>> in my-platform.target definition and I want to materialize a set of
>> products in my workspace against the specified target platform.
>>
>> That is - I want to set the target platform of my workspace to the one
>> defined in my-platform.target and materialize the workspace based on
>> some mspec/cquery.
>>
>> What are the steps I would have to perform to achieve that in headless
>> mode (e.g. perform one-click set-up of the workspace)?
>>
> You would execute two commands.
>
> buckminster importtargetdefinition my-platform.target
> buckminster import my.mspec OR my.cquery
>
> This setup will might require some redundant information though, since
> what you require for your TP can be derived from the features that you
> materialize.
>
> Regards,
> Thomas Hallgren
>
>
>
>> 14.09.2009 11:17, Thomas Hallgren kirjutas:
>>> Hi Roland,
>>> The Buckminster command 'importtargetdefinition' will import an eclipse
>>> target definition. The "materialization" as such, is performed the same
>>> way as when you set a target definition from your IDE preferences.
>>>
>>> A true Buckminster materialization can also be used to build a target
>>> platform. That has the advantage that you don't need to specify the
>>> features and bundles that should be included. Buckminster figures that
>>> out by resolving the query. You cannot use an eclipse target definition
>>> as input to this process. Instead, you would set the target platform to
>>> point to an empty directory and use an MSPEC to control which components
>>> that should end up there during materialization. The repositories that
>>> you'd use for input must be defined in an RMAP.
>>>
>>> Regards,
>>> Thomas Hallgren
>>>
>>>
>>>
>>> On 09/14/2009 10:00 AM, Roland Tepp wrote:
>>>> Hey,
>>>>
>>>> Is this possible? how woulod I go about doing this?
>>>>
>>>
>>
>>
>
|
|
|
| Re: Materializing target platform from Eclipse target definition? [message #486291 is a reply to message #485648] |
Thu, 17 September 2009 08:01 |
 Roland Tepp
Messages: 336
Registered: July 2009 |
Senior Member |
|
|
14.09.2009 13:04, Thomas Hallgren kirjutas:
> You would execute two commands.
>
> buckminster importtargetdefinition my-platform.target
> buckminster import my.mspec OR my.cquery
>
Am I right to assume that these commands are available for headless
build (I can "materialize" the target platform easily enough from the
target definition from Eclipse UI, so my first impulse to ask how do I
do it from Eclipse IDE is moot)
Other than that - if I want to execute some Buckminster commands from
Eclipse UI, I can do that only from within a component?
> This setup will might require some redundant information though, since
> what you require for your TP can be derived from the features that you
> materialize.
>
> Regards,
> Thomas Hallgren
I would guess, that in the case of workspace materialization, this is
quite okay, as in the development scenario I might need access to much
wider set of target platform plug-ins to be easily able to add new
dependencies on stuff I had before.
Another use case I see this might be useful for is that when I have a
target platform that is composed of multiple features (RCP + ECF + EMF
for example) - then I could import the entire target platform and then
in the second step, use the newly imported target platform as one of the
workspace/product materialization sources...
Does it make sanse? Can aI use it this way?
--
Roland Tepp
|
|
|
| Re: Materializing target platform from Eclipse target definition? [message #486306 is a reply to message #486291] |
Thu, 17 September 2009 08:45 |
|
Hi Roland,
On 09/17/2009 10:01 AM, Roland Tepp wrote:
> 14.09.2009 13:04, Thomas Hallgren kirjutas:
>> You would execute two commands.
>>
>> buckminster importtargetdefinition my-platform.target
>> buckminster import my.mspec OR my.cquery
>>
> Am I right to assume that these commands are available for headless
> build (I can "materialize" the target platform easily enough from the
> target definition from Eclipse UI, so my first impulse to ask how do I
> do it from Eclipse IDE is moot)
>
Yes, these commands (and all other commands I might add) are avaliable in headless mode. That has been one of the core
objects for Buckminster. Everything that you can do with it in the IDE must also be available for headless execution.
> Other than that - if I want to execute some Buckminster commands from
> Eclipse UI, I can do that only from within a component?
>
In your IDE, you will find things that corresponds to the headless commands. The 'import' for instance, is reached using
the standard context sensitive menu in your package explorer and then choosing Import. The wizard that pops up has a
Buckminster entry.
Alternatively, you right click on an MSPEC or CQUERY file, choose Buckminster and then Import.
The 'importtargetdefinition' command is essentially doing the same thing as the PDE preference settings.
A 'build' is a normal workspace build.
A 'perform' is the same as right-clicking on a project, choose 'Buckminster' -> 'Invoke Action'
etc.
>> This setup will might require some redundant information though, since
>> what you require for your TP can be derived from the features that you
>> materialize.
>>
>> Regards,
>> Thomas Hallgren
>
> I would guess, that in the case of workspace materialization, this is
> quite okay, as in the development scenario I might need access to much
> wider set of target platform plug-ins to be easily able to add new
> dependencies on stuff I had before.
>
> Another use case I see this might be useful for is that when I have a
> target platform that is composed of multiple features (RCP + ECF + EMF
> for example) - then I could import the entire target platform and then
> in the second step, use the newly imported target platform as one of the
> workspace/product materialization sources...
>
> Does it make sanse? Can aI use it this way?
>
Yes. That makes a lot of sense. You can also slam it together to one single import step and control what ends up where
by use of the mspec. You may have several such mspecs and if they share target platform artifacts, they will not be
materialized more then once since the actual TP is an artifact repository managed by P2.
Regards,
Thomas Hallgren
|
|
|
Goto Forum:
Current Time: Tue Jan 21 22:49:22 GMT 2025
Powered by FUDForum. Page generated in 10.37925 seconds |
] 
Search
Help
Register
Login
Home
