|
|
|
| Re: Headless resolve and MSPEC files [message #378946 is a reply to message #378944] |
Wed, 30 July 2008 14:16   |
 Achim Demelt
Messages: 160
Registered: July 2009 |
Senior Member |
|
|
Hi Doug,
I haven't tried it with an MSPEC that points to a CQUERY, and I'm not
familiar enough with buckminster's details to say if this is a bug or a
feature ;-)
If you want to populate your workspace, you can use the "resolve" command,
which directly takes a CQUERY as an argument. If you want to do some other
materialization, like site mirroring or target platform materialization, I
guess you'll have use "import" and provide it with an MSPEC that points to
a BOM.
To produce a BOM in headless mode, you can use the following:
buckminster -N -B my.bom my.cquery
This does not populate the workspace and writes the bom to my.bom.
HTH,
Achim
Douglas Palmer wrote:
> Thanks Achim
>
> That works with an MSPEC which specifies a BOM in it's url. However, it
> doesn't work if the url points to a CQUERY. The component meta data
> language specification says that the url can point at a BOM or a CQUERY.
> Do I need to do something different to use an MSPEC with a CQUERY?
>
> Regards
> Doug
|
|
|
|
| Re: Headless resolve and MSPEC files [message #378950 is a reply to message #378949] |
Wed, 30 July 2008 20:56 |
Achim Demelt
Messages: 160
Registered: July 2009 |
Senior Member |
|
|
Hi Doug,
No, I 'm also specifying the target path directly in the MSPEC. Albeit, to
refrain from hardcoding an arbitrary path, I have a placeholder token in my
MSPEC and I use ant's "replace" task to insert the actual path in the
process of my build.
Regards,
Achim
Douglas Palmer wrote:
> Thanks again Achim
>
> Creating a BOM first solves that problem. My only problem now is that
> importing my MSPEC installs the features into buckminster rather than my
> target platform. I guess that the targetPlatform materialiser doesn't use
> the targetPlatformPath in the same way resolve does. Do you know how to
> tell the targetPlatform materialiser where the target platform is wihout
> hardcoding it into the MSPEC?
>
> Regards
> Doug
>
>
> Achim Demelt wrote:
>
>> Hi Doug,
>
>> I haven't tried it with an MSPEC that points to a CQUERY, and I'm not
>> familiar enough with buckminster's details to say if this is a bug or a
>> feature ;-)
>
>> If you want to populate your workspace, you can use the "resolve"
>> command, which directly takes a CQUERY as an argument. If you want to do
>> some other materialization, like site mirroring or target platform
>> materialization, I guess you'll have use "import" and provide it with an
>> MSPEC that points to a BOM.
>
>> To produce a BOM in headless mode, you can use the following:
>
>> buckminster -N -B my.bom my.cquery
>
>> This does not populate the workspace and writes the bom to my.bom.
>
>> HTH,
>> Achim
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 1.35981 seconds
] 
Search
Help
Register
Login
Home
