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

Why subscribe?

20. Other Books You May Enjoy

Appendix: Contributing to CMake and Further Reading Material

Code signing for macOS

For a lot of use cases, creating unsigned apps or frameworks might be enough; however, if applications are to be distributed through the official channels for macOS, signing is a must. Signing works through Xcode itself; however, it is also possible to use CMake for signing.

To sign, there are three pieces of information needed: the ID of the bundle or framework, the development team ID, and the code signing entity. Values can be set with the XCODE_ATTRIBUTE_DEVELOPMENT_TEAM and XCODE_ATTRIBUTE_CODE_SIGN_ENTITY Xcode attributes. Typically, these are set on a project level and not for individual targets:

set(CMAKE_XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "Apple Development" CACHE STRING "")
set(CMAKE_XCODE_ATTRIBUTE_DEVELOPMENT_TEAM "12345ABC" CACHE STRING "")

The signing identity denotes the certificate provider and can usually be left as "Apple Development", which causes Xcode to select the appropriate signing...

The rest of the chapter is locked

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

Table of Contents (22) Chapters

Code signing for macOS

Unlock this book and the full library FREE for 7 days

Authors (2)

Personalised recommendations for you