![]() ![]() ![]() Using Qt Commercial was a real time saver. I could immediately build, run and deploy my example application (an Internet radio). When I started QtCreator after the installation, I was positively surprised by a complete and correct kit definition. So, I decided to use my Qt Commercial license for small businesses and to install the QBSP (Qt Board Support Package) for the Raspberry Pi 3B. When I prepared this post as a talk for Qt Day 2020, I was hard pressed for time. Nearly Automatic Configuration of QtCreator Kits In the unlikely event that we must fall back to older versions, my post Deploying Qt Projects to Embedded Devices with CMake explains a workaround. Actually, I am not aware of any reasons, why we cannot work with the latest released versions of QtCreator and CMake. We use QtCreator not older than version 4.11 and CMake not older than version 3.14. Hence, we need not enter a password every time we deploy the application to the device. In QtCreator, we have defined a Device so that we can log in the Raspberry Pi with SSH using public key authentication. We have built a Linux image and an SDK for an embedded device, e.g., a Raspberry Pi 3B. The fairly unknown script configure-qtcreator.sh from the Yocto layer meta-boot2qt automates most of the kit definition. ![]() QtCreator performs these steps in a breeze, because we spent quite some time to define a QtCreator Kit. QtCreator cross-compiles the application, deploys it to the device and runs it on the device. We change the code of our Qt application in QtCreator and press the Run button to try the changes on an embedded device. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |