Book Image

Hands-On Embedded Programming with Qt

By : John Werner
Book Image

Hands-On Embedded Programming with Qt

By: John Werner

Overview of this book

Qt is an open source toolkit suitable for cross-platform and embedded application development. This book uses inductive teaching to help you learn how to create applications for embedded and Internet of Things (IoT) devices with Qt 5. You’ll start by learning to develop your very first application with Qt. Next, you’ll build on the first application by understanding new concepts through hands-on projects and written text. Each project will introduce new features that will help you transform your basic first project into a connected IoT application running on embedded hardware. In addition to gaining practical experience in developing an embedded Qt project, you will also gain valuable insights into best practices for Qt development and explore advanced techniques for testing, debugging, and monitoring the performance of Qt applications. The examples and projects covered throughout the book can be run both locally and on an embedded platform. By the end of this book, you will have the skills you need to use Qt 5 to confidently develop modern embedded applications.
Table of Contents (22 chapters)
Free Chapter
1
Section 1: Getting Started with Embedded Qt
5
Section 2: Working with Embedded Qt
10
Section 3: Deep Dive into Embedded Qt
14
Section 4: Advanced Techniques and Best Practices
Appendix A: BigProject Requirements

Section 4: Advanced Techniques and Best Practices

Chapter 11 – Debugging, Logging, and Monitoring Qt Applications

  1. What is an SPM and how are they made?
    SPM stands for Silly Programmer Mistakes. These are common mistakes C++ programmers make that can be hard to find. They include things such as a = b instead of a == b in an if statement.
  2. Can static analysis replace code reviews? Why or why not?
    No. Static analysis is good at catching syntactical errors, while code reviews are good at catching logical errors.
  3. How much of the code should be tested?
    All of it.
  4. What is a classic Linux code coverage tool?
    gcov.
  5. Are PRINT statements still valid for debugging?
    Yes. They still have their place, especially in systems where stopping...