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

Generating code coverage reports

Being aware of how much of your code is covered by tests is a great benefit and often gives a very good impression of how well-tested a given software is. It can also give hints to developers about the execution paths and edge cases that are not covered by tests.

To get code coverage in C++

There are a few tools that help you get code coverage in C++. Arguably, the most popular is Gcov from GNU. It’s been around for years and works well with GCC and Clang. Although it does not work with Microsoft’s Visual Studio, using Clang to build and run software provides a viable alternative for Windows. Alternatively, the OpenCppCoverage tool can be used to get coverage data on Windows to build with MSVC.

The coverage information generated by Gcov can be collected in summarized reports with the Gcovr or LCOV tools.