For the moment, I only want to do a quick test of QML. Once the Qt builds are ready, it is time to run. I did not keep track of those changes, they were all trivial. Nothing particularly relevant, but I had to apply a few changes. I had a few build errors building Qt 6.2 beta3. Therefore, I suspect you have to decide if you want zstd support or not before building Qt 6 for the host, and be coherent with the build for the target. My guess is that the host tools use zstd by default to compress when available, but this is a problem when zstd is available on the host and not available on the target. According to the sources, it seems that resources are compiled by the rcc tool. I would only like to note one thing here: I had problems linking because of a missing symbol: qt_resourceFeatureZstd. Dependenciesĭependencies are already listed elsewhere. The one for Buster is the one I used in my build, and the target arch is armv8-a. Please note that those toolchains are not always able to target every arch. In the past years I had a lot of weird problems building with those toolchains, so I started to create my own. The toolchain from the host is typically provided by your distro (I used Manjaro in this case), while the toolchain to cross-build for the Raspberry Pi is officially provided here. Toolchainīuilding Qt requires a toolchain for building on the host and a toolchain to build for the target (the Raspberry Pi in this case). To start, I want to use eglfs on OpenGL ES. I configured this build in the simplest form. Instructions on how to build are already available online from many sources, so I won’t repeat the theory here. This makes a difference when trying to build it and cross-build it. Now that Qt 6.2 is almost out, I guess it is time to have a look at how Qt 6 runs on eglfs on a Raspberry Pi. It has been some time since Qt 6 was released.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |