Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311967 - Provide mechanism for sys integrators to state that pkg A depends on pkg B
Summary: Provide mechanism for sys integrators to state that pkg A depends on pkg B
Status: ASSIGNED
Alias: None
Product: RTSC
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dave Russo CLA
QA Contact:
URL:
Whiteboard: target: 3.40
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-06 16:09 EDT by Chris Ring CLA
Modified: 2014-02-26 00:56 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Ring CLA 2010-05-06 16:09:38 EDT 
There are times when pkg A depends on an interface in pkg B, but the symbols are resolved in a lib from pkg C.  E.g. my lib (pkg A) uses an OSAL where the headers are in pkg B (ti.osal.interfaces), but the implementation is in pkg C (wince.osal).  pkg A should say it depends on pkg B, but XDC needs to make sure pkg A also depends on pkg C - so that the library link order can be correct.  Only the system integrator knows that dependency.

[ Today we often solve this by adding a cfg param in pkg B that's the string pkg name of pkg C (e.g. B.delegatePkg = "wince.osal";), so in pkg B's close() it can establish a dependency (xdc.loadPackage("wince.osal");) on pkg C.  That pattern works, but is fairly advanced, and package specific.  It would be valuable to provide this feature in a more general way. ]