Myles Dear
> > > @sogloarcadius could you please validate if this was fixed in v20.1 release? Update: This request is tracked on our backlog but has not yet been released.
I am also aiming to package for Wayland / Weston. I create a packaging VM using Yocto Poky Kirkstone Linux and explicitly remove X11 collateral and explicitly add Wayland /...
For the record, here's what I get when I run the AppImage (Dice 3D/physics example that ships with Qt6) on a freshly rebooted CrossControl v700 device (i.MX8DualXPlus ARMv8 aarch64 platform):...
I tried defining the following environment variable before invoking the linuxdeploy toolchain: `export QT_QPA_PLATFORM=wayland`
I'm stuck again. I'm failing at the same point on my QEMU Yocto Poky Kirkstone build with x11 stripped out and wayland/weston added (and rebuilt completely from scratch) I'm also...
I hacked my way around this, but hope for a fix that will allow a system with no x11 support to not expect x11 libraries.
I finally got an AppImage that works on my ARMv8 target, but I had to do some manual packaging steps. This toolchain got me 95% of the way there, though,...
[ConnectionLog.txt](https://github.com/microsoft/vscode-remote-release/files/14259550/ConnectionLog.txt)
I am relying on the linuxdeploy-qt plugin, which does apparently require qmake. This issue is a placeholder, I am not experiencing any specific problem, but I have seen Qt documentation...
I also saw that the Twitter onion site has an expired certificate