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?