Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
CMake Best Practices

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

Arrow left icon
Product type Paperback
Published in Aug 2024
Publisher Packt
ISBN-13 9781835880647
Length 356 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Mustafa Kemal Gilor Mustafa Kemal Gilor
Author Profile Icon Mustafa Kemal Gilor
Mustafa Kemal Gilor
Dominik Berner Dominik Berner
Author Profile Icon Dominik Berner
Dominik Berner
Arrow right icon
View More author details
Toc

Table of Contents (22) Chapters Close

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 20. Other Books You May Enjoy Appendix: Contributing to CMake and Further Reading Material

Answers

  1. CMakePresets.json is usually maintained and delivered together with the project, while CMakeUserPresets.json is maintained by the user. Regarding the syntax and the contents, there is no difference.
  2. This can be done by calling cmake --preset=presetName, cmake --build --preset=presetName, or ctest --preset=presetName.
  3. There are configure, build, package, test, and workflow presets. Build, test, and package presets depend on a configure preset to determine the build directory.
  4. A configure preset should define a name, the generator, and the build directory to be used.
  5. The first preset to set a value takes precedence.
  6. This can be done by either using the native support of an editor for build containers, running the editor from within the container, or starting the container each time to invoke single commands inside.
  7. They define the system name, the location of the sysroot, the compilers to use, and how the find_ commands behave.
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime