Bugzilla – Full Text Bug Listing
| Summary: | Provide mechanism for sys integrators to state that pkg A depends on pkg B | ||
|---|---|---|---|
| Product: | [Technology] RTSC | Reporter: | Chris Ring <cring> |
| Component: | Core | Assignee: | Dave Russo <d-russo> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | dfriedland, gdang |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | target: 3.40 | ||
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. ]