Ian Bull wrote:
This is a good example of build overlap. There is also some discussion
on PDE/Build about using a target definition file to provision your
target before building:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311
Buckminster can manage target platform definitions from the command line. The only problem with such
a definition is that it is fairly static. The things in it cannot be determined based on a
resolution that is controlled from the top down. As a result, you often get a target platform that
contains far to much stuff and only a fragment of it will end up in your final product.
To remedy this, Buckminster is capable of populating a "Directory" location in a target platform
definition. The Buckminster resolver will determine what's needed (cannot use the planner since it
cannot manage multi platform configurations) and then we call on the P2 engine to populate the
target platform using it's collect phase.
I don't know if it makes sense for Athena to first provision your target
(and then use the results of this as a baseRepoLocation / pluginPath),
or if PDE/Build should support this internally.
The fact that this conversation is spanning 3 lists shows a great deal
of overlap between these technologies.
Yes, b3 is badly needed. I suggest that we continue this discussion on the cross project list until
the b3 list has been set up.
Regards,
Thomas Hallgren
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
