Book Image

CMake Best Practices

By : Dominik Berner, Mustafa Kemal Gilor
5 (2)
Book Image

CMake Best Practices

5 (2)
By: Dominik Berner, Mustafa Kemal Gilor

Overview of this book

CMake is a powerful tool used to perform a wide variety of tasks, so finding a good starting point for learning CMake is difficult. This book cuts to the core and covers the most common tasks that can be accomplished with CMake without taking an academic approach. While the CMake documentation is comprehensive, it is often hard to find good examples of how things fit together, especially since there are lots of dirty hacks and obsolete solutions available on the internet. This book focuses on helping you to tie things together and create clean and maintainable projects with CMake. You'll not only get to grips with the basics but also work through real-world examples of structuring large and complex maintainable projects and creating builds that run in any programming environment. You'll understand the steps to integrate and automate various tools for improving the overall software quality, such as testing frameworks, fuzzers, and automatic generation of documentation. And since writing code is only half of the work, the book also guides you in creating installers and packaging and distributing your software. All this is tailored to modern development workflows that make heavy use of CI/CD infrastructure. By the end of this CMake book, you'll be able to set up and maintain complex software projects using CMake in the best way possible.
Table of Contents (22 chapters)
Part 1: The Basics
Part 2: Practical CMake – Getting Your Hands Dirty with CMake
Part 3: Mastering the Details

Chapter 11: Automated Fuzzing with CMake

Software testing is crucial for ensuring that a software system behaves as expected. Unsurprisingly, the need for scenario-based testing strategies is still at its peak. But the scenario-based approach often does not suffice. The real world is wild. Things out there are not sterile as in a test environment. Many different variables contribute to a software's behavior. Environments, users, hardware, operating systems, or third-party libraries can affect software unexpectedly. As software becomes more extensive, it becomes painfully hard to come up with a testing suite that covers all possible aspects of it. Therefore, the need for a technique that performs the unexpected arises. Thankfully, fuzzing comes to the rescue.

In this chapter, we will learn the basics of fuzzing and learn how to use this technique to test our software to make it more reliable. Furthermore, we will learn how we can integrate fuzzing tools into CMake to easily...