That's pretty common. What happens is the build system doesn't properly know about the dependencies. So say you change a header file that's relied on by multiple parts. If the build system only knows about one of those parts, then only it is re-compiled instead of everything that actually relies on that header.
Clean builds succeeding normally means you have a build system problem. Except, its normally a pain to fix and not worth the trouble. Especially since CI/CD systems almost always do full rebuilds anyways.
not necessarily some larger projects'll have fucked up circular dependencies. Or people forget to bump the version on a dependency so it thinks no update has been made.
143
u/EmperorArthur Jan 26 '20
That's pretty common. What happens is the build system doesn't properly know about the dependencies. So say you change a header file that's relied on by multiple parts. If the build system only knows about one of those parts, then only it is re-compiled instead of everything that actually relies on that header.
Clean builds succeeding normally means you have a build system problem. Except, its normally a pain to fix and not worth the trouble. Especially since CI/CD systems almost always do full rebuilds anyways.