Separating components in the build system
Once a project reaches a certain size, it becomes rather difficult to manage as a single large project. One strategy for dealing with this is to separate the large project into small components, at least within the build system. However, this carries some risks, and it can be rather difficult to get right, particularly if the output of the large project is a shared library. One instance where these issues appear is in testing. Testing the internals of a shared library can be rather problematic, since these details might not be externally visible (exported). Sometimes these internals don’t need to be tested in isolation, but if you do, pulling these into a small static library that is linked into the larger library and tested independently is one strategy. Understanding when and how one can separate parts into their own component and how to integrate them into the larger whole is crucial to getting this right.
The key to modularizing...
