An article about static libraries, the benefits (or non-benefits) of splitting your project into static libraries, and the knock-on effects this can have on project dependencies.
by Thomas Young
From the article:
A cautionary tale about statically-linked libraries, as generated by C/C++ build tools.
As a project accumulates features, and complexity, it gets harder to understand exactly what's going on, and to find your way around the source code. You need to find some way to organise the code and try and keep things manageable.
A common idea, in this situation, is to group some source files together to split out as a static library.
I'm going to argue that this actually does very little, in itself, to increase modularity, can have the effect of significantly increasing dependencies, and is maybe not such a good idea, after all.