- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Assume that I have a IVF 10 project P, which calls subroutines from a static library L1. This static library needs subroutines defined in another static library L2. L1 and L2 have both their own module which contains explicit interface blocks for the subroutines they contain. P does not call directly any subroutine from L2.
It seems obvious that L2 is among the dependencies of L1; and that L1 is among the dependencies of P.
What is less obvious to me is that it seems that I need to declare L2 among the dependencies of P as well. Dependencies are not associative ? Am I missing something here?
(Dependenciesin the Visual Studio 2005 sense)
Thanks,
Olivier
It seems obvious that L2 is among the dependencies of L1; and that L1 is among the dependencies of P.
What is less obvious to me is that it seems that I need to declare L2 among the dependencies of P as well. Dependencies are not associative ? Am I missing something here?
(Dependenciesin the Visual Studio 2005 sense)
Thanks,
Olivier
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In IVF 10, a library dependent on another library did not cause the sub-library to be linked in. In IVF11 there's a project setting, "Link library dependencies", which controls this. This is patterned after similar functionality in Visual C++.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One more reason to upgrade... Thanks Steve!!
Olivier.
Olivier.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page