[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pde-dev] New Target API not included for M5
- From: Thomas Hallgren <thomas@xxxxxxx>
- Date: Thu, 28 Jan 2010 15:36:05 +0100
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:220.127.116.11) Gecko/20091209 Fedora/3.0-3.fc11 Lightning/1.0b1 Thunderbird/3.0
On 01/28/2010 03:29 PM, Darin Wright wrote:
Are you referring to API baselines for API tooling?
A question on the new target API.
Today it's a struggle to set up a baseline from a target definition.
Yet baselines and target definitions have a lot in common. Is this
addressed in the new target work?
Is this present already? I would like to enable easy support for this in
Buckminster. I already have headless commands for defining and importing
target definitions, but so far, nothing for the API baselines. Ideally,
I'd like to add a command saying "make this TP the workspace baseline".
If so, you are correct - an API baseline is just another target. There is
no official API for creating API baselines currently. However, in PDE, we
leverage the target implementation to populate API baselines. I.e. we
define a target, resolve the contents, and then construct an API baseline
with API components (bundles) based on the resolved bundles in a target.
Pointers to relevant code would be very helpful. Nonofficial is OK :-)