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

Creating Reproducible Build Environments

Building software can be complex, especially when dependencies or special tools are involved. What compiles on one machine might not work on another because a crucial piece of software is missing. Relying on the correctness of the documentation of a software project to figure out all the build requirements is often not enough, and consequently, programmers spend a significant amount of time combing through various error messages to figure out why a build fails.

There are countless stories out there of people avoiding upgrading anything in a build or Continuous Integration (CI) environment because they fear that every change might break the ability to build the software. This goes as far as companies refusing to upgrade the compiler toolchains they are using for fear of no longer being able to ship products. Creating robust and portable information about build environments is an absolute game-changer. With presets, CMake provides the possibility...