[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [buckminster-dev] Still fuzzy on generators/artifacts
|
Hi Todd,
I don't think the generator concept is widely used at present and I haven't got around to write any
demo sample for it just yet. We added it to support some use-cases in Buckminster that we since then
moved away from (we moved from Axis with and interfaces generated from WSDL to using JSON).
I'm more then happy to help though but in order to do that, you must tell me some more about what
specific problems that you are facing.
Regards,
Thomas Hallgren
Todd_Lee@xxxxxxxx wrote:
Hi there,
Does anybody have any examples of a component which has a dependency on a
sub-component (ie attribute) of another component which itself is a product
of an action?
i.e. -
Component A depends on Component B's 'artifact.lib' artifact.
artifact.lib is generated by an action which depends only on the source for
the binary and the ant actor that builds it.
I'm trying to manually write the buckminster cspecs (they're non-java
components) for 'A' and 'B' above so that when B is resolved as a
dependency of A, 'artifact.lib' is automatically built by the actor that
generates it... Is this possible?
Any help is greatly appreciated.
T
Todd Lee
Software Tools
ON Semiconductor
Tel: +1.519.884.9696 ext 2242
Fax: +1.519.884.0228
E-mail: todd_lee@xxxxxxxx
Todd_Lee@xxxxxxxx
Sent by:
buckminster-dev-b To
ounces@xxxxxxxxxx buckminster-dev@xxxxxxxxxxx
g cc
Subject
04/10/2008 04:13 [buckminster-dev] question about
PM generators and/or 'just in time'
building of dependencies
Please respond to
Buckminster
developer
discussions
<buckminster-dev@
eclipse.org>
I've got a couple of non-java (python) projects that I'm trying to
'buckminsterize' - The relation is something like this:
Component A depends on artifact X contained in Component B
So I've set up the dependencies so that when I call my top level cquery
(dependent on Component A) I get a workspace with both Component A and
Component B materialized (I'm working in the IDE right now). I've created
buckminster.cspec's for both components as well as build.xml wrappers for
the actual python build operations.
I'm wondering if there's a way (I'm sure there must be, so I guess the
question is really 'what's the recommended way') to build Component B so
that artifact X is ready and waiting when Component A looks for it to
fulfill the build-time dependency? Looking at the documentation, it would
seem that perhaps this is the role of the 'generator' element in the cspec,
but I'm not clear on how it should be implemented. Any help would be
greatly appreciated.
Thanks!
Todd
Todd Lee
Software Tools
ON Semiconductor
Tel: +1.519.884.9696 ext 2242
Fax: +1.519.884.0228
E-mail: todd_lee@xxxxxxxx
_______________________________________________
buckminster-dev mailing list
buckminster-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/buckminster-dev