You're reading from CMake Best Practices Upgrade your C++ builds with CMake for maximum efficiency and scalability

Product type Paperback

Published in Aug 2024

Publisher Packt

ISBN-13 9781835880647

Length 356 pages

Edition 2nd Edition

Languages

C++

Tools

Cmake

Concepts

Application Development

Authors (2):

Mustafa Kemal Gilor

Dominik Berner

View More author details

Table of Contents (22) Chapters

Preface

1. Part 1 – The Basics

2. Chapter 1: Kickstarting CMake FREE CHAPTER

3. Chapter 2: Accessing CMake in the Best Ways

4. Chapter 3: Creating a CMake Project

5. Part 2 – Practical CMake – Getting Your Hands Dirty with CMake

6. Chapter 4: Packaging, Deploying, and Installing a CMake Project

7. Chapter 5: Integrating Third-Party Libraries and Dependency Management

8. Chapter 6: Automatically Generating Documentation

9. Chapter 7: Seamlessly Integrating Code Quality Tools with CMake

10. Chapter 8: Executing Custom Tasks with CMake

11. Chapter 9: Creating Reproducible Build Environments

12. Chapter 10: Handling Distributed Repositories and Dependencies in a Super-Build

13. Chapter 11: Creating Software for Apple Systems

14. Part 3 – Mastering the Details

15. Chapter 12: Cross-Platform-Compiling Custom Toolchains

16. Chapter 13: Reusing CMake Code

17. Chapter 14: Optimizing and Maintaining CMake Projects

18. Chapter 15: Migrating to CMake

19. Index

Why subscribe?

20. Other Books You May Enjoy

Appendix: Contributing to CMake and Further Reading Material

Optimizing and Maintaining CMake Projects

Software projects tend to live for a long time, and for some, it’s not unheard of for them 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 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 project...