Linked by Thom Holwerda on Wed 24th Jun 2009 12:24 UTC, submitted by ralsina
Permalink for comment 370395
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
More News »
Sponsored Links



Member since:
2008-04-29
If you're a programmer, I'm sure you'll be aware that not all libraries are designed to be linked statically. For instance, many features of the Qt toolkit are unavailable when linked statically.
What's more, if a library is statically linked, and a new version of the library is released, it means that the whole application must be relinked (and probably recompiled) in order to update it. If the library were linked dynamically, it would be possible to simply replace the library file in the package before distributing it, which is far easier.