You're reading from CMake Best Practices Discover proven techniques for creating and maintaining programming projects with CMake

Product type Paperback

Published in May 2022

Publisher Packt

ISBN-13 9781803239729

Length 406 pages

Edition 1st Edition

Tools

Cmake

Concepts

Application Development

Authors (2):

Dominik Berner

Mustafa Kemal Gilor

Preface

1. Part 1: The Basics

2. Chapter 1: Kickstarting CMake FREE CHAPTER

3. Chapter 2: Accessing CMake in 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 with CMake

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 Big Projects and Distributed Repositories in a Superbuild

13. Chapter 11: Automated Fuzzing with CMake

14. Part 3: Mastering the Details

15. Chapter 12: Cross-Platform Compiling and Custom Toolchains

16. Chapter 13: Reusing CMake Code

17. Chapter 14: Optimizing and Maintaining CMake Projects

18. Chapter 15: Migrating to CMake

19. Chapter 16: Contributing to CMake and Further Reading Material

20. Assessments

21. Other Books You May Enjoy

Chapter 12, Cross-Platform-Compiling Custom Toolchains

Toolchain files are passed either by the --toolchain command-line flag, the CMAKE_TOOLCHAIN_FILE variable, or with the toolchainFile option in a CMake preset.
Usually, the following things are done in a toolchain file for cross-compiling:
1. Defining the target system and architecture
2. Providing paths to any tools needed to build the software
3. Setting default flags for the compiler and linkers
4. Pointing to the sysroot and possibly any staging directory if cross-compiling
5. Setting hints for the search order for any find_ commands of CMake
The staging directory is set with the CMAKE_STAGING_PREFIX variable and is used as a place to install any built artifacts if the sysroot should not be modified.
The emulator command is passed as a semicolon-separated list in the CMAKE_CROSSCOMPILING_EMULATOR variable.
Any call to project() or enable_language() in a project will trigger detection of the features.
The configuration...

The rest of the chapter is locked