Lee, I think that one of the main reasons open source software often uses static libraries, especially on Windows, is that it gets around a lot of the dependency issues. You don't have to worry about dynamically loading a strange version of a dependency library if you never dynamically load libraries. CoApp intends to solve this problem so I think developers should choose to release non-statically bound libraries whenever possible and hopefully they will.
Eric On Fri, Oct 1, 2010 at 12:36 PM, Lee Fisher <blib...@gmail.com> wrote: > Certainly CoApp supports the use of static libraries; >> > > Excellent news, thanks. > > and there is really only a small set of really valuable reasons one might >> want to use static code. >> >> The top of that list, is[...] >> > > that the compiler and operating system support the use of static libs, and > existing software use them, so CoApp should try to support the platforms' > tools and existing projects, and not cause additional restrictions that'll > prevent adoption of this toolchain. IMO, at least. :-) > > > _______________________________________________ > Mailing list: https://launchpad.net/~coapp-developers > Post to : coapp-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~coapp-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
