We need to be able to build Qt/QtWebEngine for all supported Raspberry Pi boards (with the appropriate Qt device profile).The process must be fully automated from start to finish.We sat down and created the following requirements for our build process: Since these projects share no code base, this was a greenfield opportunity that allowed us to start afresh and explore exciting new technologies for the build process.īecause compiling Qt (and QtWebEngine) is a very heavy operation, we would need to pre-compile and distribute Qt so that the Dockerfile could simply download and include it in the build process (rather than compiling as part of the installation process). Recently, we decided to migrate our open source digital signage software ( Screenly OSE) to Qt as well. We migrated to Qt for our commercial digital signage software a number of years ago, and since then, we have been very happy with both its performance and flexibility. The countless blog posts, forum threads, and Stack Overflow posts on the topic reveal that compiling Qt is a common headache.Īs long-term Qt users, we have had our fair share of battles with it at Screenly. One thing you cannot say about the Qt framework, however, is that it is easy to compile - at least for embedded devices.
Find Viktor on Twitter those not familiar with Qt, it is a cross-platform development framework that is used in a wide range of products, including cars ( Tesla), digital signs ( Screenly), and airplanes ( Lufthansa). Screenly is the most popular digital signage product for the Raspberry Pi. This is a guest post from Viktor Petersson, CEO of Screenly.io.
0 kommentar(er)
