On Aug 12, 2012, at 14:33 , Stephen Kay < email@hidden> wrote: If this proprietary library is only to be used by the instance of my
application, and not shared with any other apps, then it should be a static
library?
I think the short answer is, "Yes".
If the library is not going to be shared with other apps, then I can't think of any generic reason for making it dynamic. There are probably a few specific use-cases for private dynamic libraries, but I think you would know if any of them applied here:
1. You had a reason for keeping the library code out of memory until/unless it was actually used.
2. You wanted to choose between alternate dynamic libraries at run-time.
3. You wanted to mess with symbol resolution before the library was loaded.
4. You wanted to share the library between the app and any plugin bundles.
(That sort of thing, etc. I can't say I've ever had to do any of these things.)
|