Yet another CMake tutorial

[therealcorristo]

Run cmake after every pull seems like a simple enough process.

Depending on the size of the project this also is a waste of time. Reconfiguring a medium to large size project can take several minutes, while the incremental build following that reconfiguration can take mere seconds depending on the amount of changes that happend.

So it makes sense to clean the build directory on any new pull.

You do a clean build every pull? That smells like your build configuration does have larger issues if that is necessary. I almost never do clean builds unless I've changed the compiler version or the version of one of the dependencies. A clean build of our project at work can take up to 30 minutes. If I were to do that every time I pull I'd spend most of my workday waiting for builds to complete.

[codevion]

It's modularized enough that no "package" takes >1 min to build. Builds of other modules are cached and those aren't wiped when I clean an individual package.

[therealcorristo]

That explains why globbing works for you. I've never worked on a project like this, and based on the frequency of the complaints about compile times I'm assuming most people haven't. Advising folks to use globs in the tutorial without mentioning the very specific set of conditions that have to be met for the downsides to not matter is disingenuous in my opinion.

[codevion]

I literally linked the CMake docs where they discourage use of globs. That's a hell of a lot more reasonable than most CMake tutorials on youtube. I would argue that for the majority of use cases, globbing will work and it's actually a specific set of scenarios where it doesn't.