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

Using build containers with CMake

Containerization brings the benefit that developers can control the build environment to some extent. Containerized build environments are also a tremendous help for setting up CI environments. There are quite a few container runtimes out there, with Docker being the most popular. It would exceed the scope of this book to look at containerization in depth, so we will use Docker for the examples in this book.

A build container contains a fully defined build system including CMake and any tools and libraries needed to build a certain software. By providing the container definition (for example, the Dockerfile), along with the project, or over a publicly accessible container registry, anyone can use the container to build the software. The huge advantage is that developers do not need to install and possibly pollute their host machine by installing additional libraries or tools except the software needed to run the containers. The downside is that...