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
Section 1: Getting Started with Embedded Qt
Section 2: Working with Embedded Qt
Section 3: Deep Dive into Embedded Qt
Section 4: Advanced Techniques and Best Practices
Appendix A: BigProject Requirements


  1. What is the name of the process where software is continuously integrated, built, and tested is called
  2. Why should code be integrated often and as soon as possible?
  3. What kind of software architecture can be used to separate the display of data from the code that provides the data?
  4. Why do all the code examples use m_ as the prefix to class member variables?
  5. How do you run code on the target instead of the host?
  6. What is Dependency Injection?
  7. What is mocking?
  8. Why is testing and debugging at an early stage important?
  9. Does the author's source listing always execute as expected?
  10. How well does the implemented code fit into the Presentation-Data-Hardware layer model?