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):

Berner

Mustafa Kemal Gilor

Preface

1. Part 1 – The Basics FREE CHAPTER

2. Chapter 1: Kickstarting CMake

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

20. Other Books You May Enjoy

Appendix: Contributing to CMake and Further Reading Material

Answers

The following are the answers to this chapter’s questions:

Commands that are added with add_custom_command are executed at build time, while commands that are added with execute_process are executed at configuration time.
One signature is used to create custom build steps, while the other is used to generate files.
Only POST_BUILD is reliably supported across all generators.
Variables can be defined either as ${VAR} or @VAR@.
Variable substitution can be controlled by either passing @ONLY, which only replaces variables defined as @VAR@, or by specifying the COPYONLY option, which does not perform any substitution at all.
With cmake -E, common tasks can be executed directly. With cmake -P, .cmake files can be executed as scripts.