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)
Part 1: The Basics
Part 2: Practical CMake – Getting Your Hands Dirty with CMake
Part 3: Mastering the Details


In this chapter, you learned about some concepts and strategies for migrating projects of various sizes to CMake. The effort and actual work to be done when migrating projects to CMake will very much depend on the individual setup of a project. However, with the approaches described here, choosing the right strategy will hopefully be easier. Changing the build processes and developer workflow is often disruptive, so you have to carefully consider whether the effort is worth it. Nevertheless, switching a project to CMake will open up the possibilities of all the features and practices for building quality software, as described in this book. Additionally, having a clean and well-maintained build system to work with will allow developers to focus on their main task, which is writing code and shipping software.

This brings us to the final chapter of this book, which is about getting access to the CMake community, finding further reading material, and contributing to CMake...