Book Image

CMake Best Practices

By : Dominik Berner, Mustafa Kemal Gilor
5 (2)
Book Image

CMake Best Practices

5 (2)
By: Dominik Berner, Mustafa Kemal Gilor

Overview of this book

CMake is a powerful tool used to perform a wide variety of tasks, so finding a good starting point for learning CMake is difficult. This book cuts to the core and covers the most common tasks that can be accomplished with CMake without taking an academic approach. While the CMake documentation is comprehensive, it is often hard to find good examples of how things fit together, especially since there are lots of dirty hacks and obsolete solutions available on the internet. This book focuses on helping you to tie things together and create clean and maintainable projects with CMake. You'll not only get to grips with the basics but also work through real-world examples of structuring large and complex maintainable projects and creating builds that run in any programming environment. You'll understand the steps to integrate and automate various tools for improving the overall software quality, such as testing frameworks, fuzzers, and automatic generation of documentation. And since writing code is only half of the work, the book also guides you in creating installers and packaging and distributing your software. All this is tailored to modern development workflows that make heavy use of CI/CD infrastructure. By the end of this CMake book, you'll be able to set up and maintain complex software projects using CMake in the best way possible.
Table of Contents (22 chapters)
1
Part 1: The Basics
5
Part 2: Practical CMake – Getting Your Hands Dirty with CMake
14
Part 3: Mastering the Details

Chapter 14: Optimizing and Maintaining CMake Projects

Software projects tend to live for a long time and for some, it's not unheard of to be under more or less active development for a decade or more. But even if projects do not live that long, they tend to grow over time and attract certain clutter and legacy artifacts. Often, maintaining a project does not just mean refactoring code or adding a feature once in a while, but also keeping the build information and dependencies up to date.

As projects grow in complexity, build times often increase dramatically to the point that development might get tedious because of the long wait times. Long build times are not just inconvenient, they might also encourage developers to take shortcuts because they make trying things out hard. It is hard to try out something new if each build takes hours to complete and if each push to the CI/CD pipeline takes hours to return, which does not help either.

Apart from choosing a good, modular...