[solved] Trigger action for another component from cspex [message #725174] |
Wed, 14 September 2011 07:04 |
Christian Pontesegger Messages: 250 Registered: July 2009 Location: Graz, Austria |
Senior Member |
|
|
I am trying to build an RCP with buckminster. Therefore I have my own "releng" feature project with a cspex file in it.
There exists another feature project "p2.updatesite" that creates - as the name suggests - an update site repository.
Now I want my custom action in releng to first trigger p2.updatesite -> site.p2 and use that resulting repository for its build process.
Where, and how would I trigger such a build? I see there are dependencies and prerequisites but I could not find out, how to put things together.
thanks for help
Christian
[Updated on: Wed, 14 September 2011 12:29] Report message to a moderator
|
|
|
|
|
Re: Trigger action for another component from cspex [message #725900 is a reply to message #725321] |
Fri, 16 September 2011 06:41 |
Christian Pontesegger Messages: 250 Registered: July 2009 Location: Graz, Austria |
Senior Member |
|
|
Carsten Reckord wrote on Wed, 14 September 2011 10:04
Actually, that snippet would attempt to trigger two actions, p2.updatesite
and site.p2, both in the current component.
Thanks for clarifying things here. So the attribute name always refers to an action on the current component.
What about the properties file passed to the original action? Can it be replaced for the prerequisites?
What I want to do is build an p2 update site first, followed by an RCP. All by triggering one action.
While site.p2 should be built with target.os=* RCP needs some dedicated target.os
So I have 2 actions, 1 property and 2 different values it should hold. AFAIK ant properties are immutable. Is there some neat buckminster magic that can do the trick?
[Updated on: Fri, 16 September 2011 06:41] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.03754 seconds